1509732 - JavaScript error: chrome://global/content/bindings/radio.xml, line 29: TypeError: control.radioChildConstructed is not a function

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Jorg K (CEST = GMT+2)]

Seen 300 times here:
https://taskcluster-artifacts.net/HgnhMwz_SdKjAKqQWVQxkw/0/public/logs/live_backing.log

Aceman reckons it might be related to TB's overlay loader.

Brian, is this still related to bug 1470242 as stated in bug 1496704 comment #4?

Comment 1

[:aceman]

We don't know if it relates to the custom overlay loader, but the error only shows when lightning is enabled or another addon using radio elements (and overlays).

In base TB radio elements work cleanly (e.g. in preferences).

Comment 2

[Geoff Lankow (:darktrojan)]

It's definitely coming from Lightning - there are 8 radios on the tasks tab, 4 on the calendar tab, and 12 warnings at startup. I think there's a good chance it's something to do with the radios beginning life in a different document.

Comment 3

[Brian Grinstead [:bgrins]]

Is this still happening? It could potentially be related to bug 1470242, but the basic gist is that it looks like they are inside a <radiogroup> that hasn't been upgraded as a Custom Element for some reason. I don't know if it'll change anything, but I'm marking See Also for Bug 1495861 which is going to migrate <radio> out of XBL and into a Custom Element.

Comment 4

[:aceman]

That's quite possible. If you have custom elements inside XBL-defined elements, then from the constructor of the XBL binding (or a similar good place) you need to call customElements.upgrade() on the custom elements to get them to instantiate and get their methods working.

Comment 5

[Jorg K (CEST = GMT+2)]

I haven't see it for a while and checking with a local debug build and also all Mozmill logs, I can't see it. Case closed. Thanks for the follow-up.