Skip to content

Only generate an attribute prefix if required#30

Open
bwrrp wants to merge 1 commit into
w3c:gh-pagesfrom
bwrrp:preserve-attribute-prefixes
Open

Only generate an attribute prefix if required#30
bwrrp wants to merge 1 commit into
w3c:gh-pagesfrom
bwrrp:preserve-attribute-prefixes

Conversation

@bwrrp
Copy link
Copy Markdown

@bwrrp bwrrp commented Jul 13, 2017

If implemented as specified, the prefix set for an attribute in the DOM would never be preserved during serialization. This change only generates the new prefix if the prefix is either missing (which is not allowed for namespaced attributes), or if it conflicts with another local namespace definition of the prefix for a different namespace.

Fixes #29

If implemented as specified, the prefix set for an attribute in the DOM
would never be preserved during serialization. This change only
generates the new prefix if the prefix is either missing (which is not
allowed for namespaced attributes), or if it conflicts with another
local namespace definition of the prefix for a different namespace.

Fixes w3c#29
@bwrrp bwrrp force-pushed the preserve-attribute-prefixes branch from eae9f35 to 97e7bb3 Compare October 31, 2018 11:13
@cscott
Copy link
Copy Markdown

cscott commented Jul 2, 2021

I verified that this spec change matches what Firefox currently does (see comment on issue #29). A corresponding patch would need to be made to web-platform-tests (also described at issue #29).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Serialization algorithm never preserves attribute prefixes

2 participants