Closed Bug 1419660 Opened 7 years ago Closed 6 years ago

Track performance for creating a built-in custom elements doesn't match CE definition

Categories

(Core :: DOM: Core & HTML, enhancement, P2)

Product:
Core
Component:
DOM: Core & HTML
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1419661

People

(Reporter: jdai, Unassigned)

References

Details

+++ This bug was initially created as a follow-up of bug 1299363 comment #77 +++

* We should measure where the overhead comes from in the "have second arg with is=, no define() calls" case that's measuring ~3200 in the numbers above.  Seems a bit fishy that it would be that high.

Performance detail result:
https://docs.google.com/a/mozilla.com/spreadsheets/d/1OLntq8Qd4e4td7ml6iq0r1sVxl4phMta3HFAAMvpAms/edit?usp=sharing
This bug is for creating a customized built-in custom elements doesn't match CE definition. We can track performance when CE preference is on/off for document.createElement("div", { is: "x-bar" }).
Summary: When custom elements preference is on, createElement have second arg with is=, no define() calls shouldn't much slower → Track performance for creating a built-in custom elements doesn't match CE definition
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.