Open Bug 1833878 Opened 2 years ago

Remove range workaround in parseXULToFragment

Categories

(Toolkit :: UI Widgets, task)

task

Tracking

()

People

(Reporter: bgrins, Unassigned)

References

(Blocks 1 open bug)

Details

We have this unusual workaround at the bottom of parseXULToFragment which was added to work around how XBL worked: https://searchfox.org/mozilla-central/rev/2ca95198a2a0806de358a0484d96d4354e3cbaab/toolkit/content/customElements.js#572-576. This was used to get access to the element without touching it with JavaScript (and thus eagerly constructing XBL elements before layout).

I don't see any reason why this would still be needed, and there may be a small perf win from removing it.

You need to log in before you can comment on or make changes to this bug.