8000 Use DOM definition of Attr/reflect by dontcallmedom · Pull Request #8575 · whatwg/html · GitHub
[go: up one dir, main page]

Skip to content

Conversation

dontcallmedom
Copy link
Contributor
@dontcallmedom dontcallmedom commented Dec 1, 2022

While it doesn't export it, the HTML spec currently redefines the 'reflect' concept, which creates possibly confusing duplication with the definition in the DOM spec. This proposes to use instead the DOM spec definition.

It doesn't remove the local explanation since at the moment it is part of a dedicated section on the topic.

This was noticed in w3c/mathml-core#179


/canvas.html ( diff )
/common-dom-interfaces.html ( diff )
/common-microsyntaxes.html ( diff )
/dom.html ( diff )
/edits.html ( diff )
/embedded-content-other.html ( diff )
/embedded-content.html ( diff )
/form-control-infrastructure.html ( diff )
/form-elements.html ( diff )
/forms.html ( diff )
/grouping-content.html ( diff )
/iframe-embed-object.html ( diff )
/image-maps.html ( diff )
/infrastructure.html ( diff )
/input.html ( diff )
/interaction.html ( diff )
/interactive-elements.html ( diff )
/media.html ( diff )
/obsolete.html ( diff )
/scripting.html ( diff )
/semantics.html ( diff )
/tables.html ( diff )
/text-level-semantics.html ( diff )
/urls-and-fetching.html ( diff )

While it doesn't export it, the HTML spec currently redefines the 'reflect' concept, which creates possibly confusing duplication with the definition in the DOM spec. This proposes to use instead the DOM spec definition.

This was noticed in w3c/mathml-core#179
@domenic
Copy link
Member
domenic commented Dec 1, 2022

This seems incorrect? The two definitions are totally different. The DOM one is only meant for use by DOM (which is why it's not exported); the HTML one is the one other specs should use.

@dontcallmedom
Copy link
Contributor Author

The DOM one is only meant for use by DOM (which is why it's not exported); the HTML one is the one other specs should use.

This may be the intent, but the specs are marked up exactly the other way (hence my assumption behind the PR):

annevk added a commit to whatwg/dom that referenced this pull request Feb 22, 2023
Stop exporting it as per discussion in whatwg/html#8575.
@annevk
Copy link
Member
annevk commented Feb 22, 2023

@fred-wang what does MathML need from reflect? Just the top-level definition or should some of the other concepts also be exported?

annevk added a commit to whatwg/dom that referenced this pull request Feb 22, 2023
Stop exporting it as per discussion in whatwg/html#8575.
@fred-wang
Copy link
Contributor

@annevk I guess @bkardell would know better the details, but the rule of thumb is that MathML tries to align on HTML so we probably want the HTML definition for MathML. And currently, it's only used in one place for attributes that exist in HTML (from GlobalEventHandlers and HTMLOrForeignElement), so only the top-level definition: https://w3c.github.io/mathml-core/#dom-and-javascript

@annevk
8035 Copy link
Member
annevk commented Feb 24, 2023

I see, thanks!

That usage seems bogus so I filed w3c/mathml-core#188.

Closing this for now. We might still export it, but that would require a different PR.

@annevk annevk closed this Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0