Re: Obscure error in FF20
Arnaud Didry <[email protected]> Mon, 15 Apr 2013 10:08:28 -0700 (PDT)
| Newsgroups | gmane.comp.mozilla.devel.dom |
|---|---|
| Message-ID | <[email protected]> |
Hi Boris,
Thank you for your response, I filed a ticket on bugzilla : https://bugzill=
a.mozilla.org/show_bug.cgi?id=3D861947
We don't have much more informations, but we're now sure that the error hap=
pens on this check `node.id.tagName`. Hope this helps a little.
For now we are going to monkey patch YUI3 to remove the checks against IE<8=
for FF20.
Thanks
Arnaud
Le vendredi 12 avril 2013 20:14:09 UTC+2, Boris Zbarsky a =E9crit=A0:
> On 4/12/13 6:49 AM, Arnaud Didry wrote:
> =
> > We are experiencing random and obscure errors since the FF20 update : "=
TypeError: Value does not implement interface Element".
> =
> =
> =
> That's certainly the error you'd get if something that's not an element =
> =
> has an element method called on it...
> =
> =
> =
> > The stack trace always point to the same line of code : `if (node.id &&=
!node.id.tagName && !node.id.item) {id =3D node.id;}` (from YUI3 [1]). The=
caller also ensure that `node.nodeType =3D=3D=3D 1` [2]
> =
> =
> =
> That's quite odd, for sure!
> =
> =
> =
> Are you able to log any information about this when it fails? Knowing =
> =
> node.localName would really help.
> =
> =
> =
> > We're still trying to find a way to produce a failing test case. We dep=
loyed a patch which wrap the line in a try/catch to log the `node` variable=
but since then the error doesn't seems to occur anymore.
> =
> =
> =
> _That_ indicates some sort of JIT bug to me, unfortunately. :( I guess =
> =
> that answers my question about logging...
> =
> =
> =
> What if you put the try/catch higher up the callstack?
> =
> =
> =
> > Should I file a ticket on bugzilla ?
> =
> =
> =
> Please, with whatever information you have!
> =
> =
> =
> -Boris