Treat a null elementNs in getPropertyType/geAtributeType as the HTML … #557
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.
…namespace
This is the behavior that Chromium and WebKit currently implement, see https://phabricator.services.mozilla.com/D226547
Currently, it seems that the "interface for localName and elementNs" would fallback to
Element
, similarly to what happens withdocument.createElementNS(null, "div")
for example.Note that a null attrNs is already handled by the spec.
See also #553 for details.
Preview | Diff