I'm currently working on an ajax framework (forms, and so on) and I'm
targetting firefox 1.5 _only_.
I'm quite cautious with how I handle objects: nice encapsulation (either
with prototypes or with functions a la GTK+), as few closures as
possible, some expandos to attach field definitions to input elements,
very few global vars. And event bubbling to attach as few events as
possible to forms and tables.
I'm using E4X with 1.5beta2, and I find it less likely to crash than
beta1, where I was experiencing daily crashes in complex queries.
Now with my doubts.
1) I'd like to know if, at the moment, E4X is considered stable enough
for production use. My customers will use this program for many hours a
day, and all xmlhttp responses are converted to xml literals. I'd rather
not revert to xpath.
3) I have an issue with populating radio boxes. My form contains a
<fieldset name="foo"> element that is populated client-side with <input
type="radio" name="foo"> elements. Everything works perfectly if I give
a name="bar" to the input elements. Whenever I give name="foo" to input
elements, firefox loops forever.
Is this something I should report to bugzilla, or is there an inherent
problem with having other elements named the same as radio buttons?
I've tried calling removeAttribute('name') to the fieldset element,
after reading it, but the loop remains.
to many of my document elements. I had an epiphany when it became clear
that I could do that, and keep the code much simpler. Having relatively
should know of?
By the way, I'm serving pages with XHTML 1.1 DTD, but content-type as
text/html (yes, I shouldn't, but I have to).
really more than meets the eye.. but you already know that.
Cross post and followup-to to netscape.public.mozilla.dom
Marco Mariani wrote:
> 3) I have an issue with populating radio boxes. My form contains a
> <fieldset name="foo"> element that is populated client-side with <input
> type="radio" name="foo"> elements. Everything works perfectly if I give
> a name="bar" to the input elements. Whenever I give name="foo" to input
> elements, firefox loops forever.
Let's take that to the proper group, the DOM group.
Can you post a URL to a minimal test case showing the problem?
Have you tried your code with other browsers, do they loop too?
And why do you need and use a name attribute on <fieldset> elements?
There is no name attribute defined for that, see
Not that it should cause problems if you use one but perhaps your
problem goes away if you use proper markup.
>> I'm using E4X with 1.5beta2, and I find it less likely to crash than
>> beta1, where I was experiencing daily crashes in complex queries.
> If you want to help here, you'll have to post testcases, or at least
> talkback identifiers, so we can try to diagnose the crashes by their
> stack backtraces. Was talkback sent?
Sorry, I did't think of tallkback because I usually compile firefox
I've just sent a report of a repeatable crash I have with 1.5b2/win.