Clarity on Safari support for custom elements#38727
Merged
Conversation
Moved the note about Safari's lack of support for customized built-in elements to follow that section, making it clear that only this specific type is unsupported, while autonomous custom elements are supported.
Contributor
|
Preview URLs Flaws (3)URL:
|
Josh-Cena
approved these changes
Mar 20, 2025
wbamberg
added a commit
to wbamberg/content
that referenced
this pull request
Apr 4, 2025
* upstream/main: (172 commits) chore: improve code style guide (mdn#38715) fix: typo on `Error.isError()` page (mdn#38754) plural consistency (mdn#38747) fix: auto-cleanup by bot (mdn#38695) Synchronize with BCD v5.7.4 (mdn#38709) Add docs for JS self-profiling API (mdn#37796) Better SameSite docs (mdn#38710) Added missing explanation for Array Literals (mdn#38745) Add a page on CSRF (mdn#38151) Fix description of several Range methods (mdn#38518) Remove extraneous span (mdn#38696) Add a definition for media containers, improve how the media files are defined and Remove wrong information (mdn#38721) Move visited selector guide to CSS selectors module (mdn#38642) Make JSON learning article more technically precise (mdn#38644) Make translate3d() interactive example code valid (mdn#38647) Clarity on Safari support for custom elements (mdn#38727) feat(css): Link to learning doc about text direction (mdn#38719) Fix typo (mdn#38739) move guide to module: inline formatting context (mdn#38637) Fix CSS pseudo-class lists (mdn#38576) ...
cssinate
pushed a commit
to cssinate/content
that referenced
this pull request
Apr 11, 2025
Moved the note about Safari's lack of support for customized built-in elements to follow that section, making it clear that only this specific type is unsupported, while autonomous custom elements are supported.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Moved the note about Safari's lack of support for customized built-in elements to follow that section, making it clear that only this specific type is unsupported, while autonomous custom elements are supported.
Motivation
To reduce confusion for users that are new to custom elements, to make it clear that Safari supports custom components.
Additional details
https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define
Related issues and pull requests
n/a