Closed Bug 1659410 Opened 4 years ago Closed 4 years ago

Resolve with the class used to define the Custom Element

Categories

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

79 Branch
enhancement

Tracking

()

RESOLVED FIXED
83 Branch
Tracking Status
firefox83 --- fixed

People

(Reporter: andrea.giammarchi, Assigned: emilio)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

Steps to reproduce:

  1. define a custom element
  2. analyze whenDefined resolved callback
  3. find nothing passed along the resolved callback

Actual results:

whenDefined resolves with undefined.

Expected results:

Accordingly with https://github.com/whatwg/html/issues/5552, whenDefined should resolve with the class used to define the custom element in the registry.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
Assignee: nobody → emilio
Status: UNCONFIRMED → ASSIGNED
Depends on: 1659403
Ever confirmed: true

James, do you know why bug 1659403 hasn't been closed even though the tests have been synced for a while?

Flags: needinfo?(james)
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5bb7ed8a23d0 Resolve whenDefined promises with custom element constructor. r=edgar

That was one of the syncs where we dropped some PRs I think, and the cleanup didn't close the bugs. I can look at that.

Flags: needinfo?(james)
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: