Page MenuHomePhabricator

Bug 1629761 - Should not invoke attributeChangedCallback for the attribute that is changed during upgrading;
ClosedPublic

Authored by edgar on Apr 15 2020, 11:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 3, 6:10 AM
Unknown Object (File)
Oct 15 2025, 5:22 PM
Unknown Object (File)
Sep 25 2024, 9:57 AM
Unknown Object (File)
Aug 6 2024, 6:09 AM
Subscribers
None

Details

Summary

In https://dom.spec.whatwg.org/#handle-attribute-changes, the attributeChangedCallback
reaction is enqueued only if the custom-element-state is customized.

And the assumption of "custom-element-definition is only available on the element whose
custom-element-state is customized" is no longer true after bug 1610054 along with the
spec changings in https://github.com/whatwg/html/pull/5126.

Diff Detail

Event Timeline

phab-bot changed the visibility from "Custom Policy" to "Public (No Login Required)".
phab-bot changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
phab-bot removed a project: secure-revision.
edgar added a reviewer: smaug.
This revision is now accepted and ready to land.Apr 15 2020, 12:46 PM
edgar edited the summary of this revision. (Show Details)
edgar edited the summary of this revision. (Show Details)

Do we need the patch in branches?

Yes, at least in beta.

dom/base/Element.cpp
2335

Done.