Closed
Bug 1481714
Opened 7 years ago
Closed 7 years ago
TypeError: actors is undefined: onCustomElementDefined
Categories
(DevTools :: Inspector, enhancement, P3)
DevTools
Inspector
Tracking
(firefox63 fixed)
RESOLVED
FIXED
Firefox 63
Tracking | Status | |
---|---|---|
firefox63 | --- | fixed |
People
(Reporter: jdescottes, Assigned: jdescottes)
References
Details
Attachments
(1 file)
Even though we make sure we always have a registry map, we might send an element-defined event with a null actors argument.
This results in an error in the listener defined in walker.js:
https://searchfox.org/mozilla-central/rev/f0c15db995198a1013e1c5f5b5bea54ef83f1049/devtools/server/actors/inspector/walker.js#357-361
The reason for this is that the event we added on platform side gets fired whether or not we have seen elements with a given name. This was not the case with the temporary implementation I used to do most of the development.
I think we should still fire the event, but with an empty Set(). On top of that, I think we should also emit the name of the custom element that was defined.
Assignee | ||
Updated•7 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•7 years ago
|
||
![]() |
||
Comment 2•7 years ago
|
||
Comment on attachment 8998432 [details]
Bug 1481714 - Fix actors is null error when custom element is defined;r=ladybenko
Belén [:ladybenko] has approved the revision.
Attachment #8998432 -
Flags: review+
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/18573457af6a
Fix actors is null error when custom element is defined;r=ladybenko
![]() |
||
Comment 4•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
You need to log in
before you can comment on or make changes to this bug.
Description
•