-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore serialization of CDATASection nodes #38
Labels
Comments
The serialization steps were in a comment which was removed, but they can still be found at Line 1510 in ab8d1ac
(and in the code for w3c-xmlserializer, which github has helpfully linked above). Do we need to throw an exception if requireWellFormed is set and the node data contains the string |
wmfgerrit
pushed a commit
to wikimedia/mediawiki-libs-Dodo
that referenced
this issue
Jul 3, 2021
Bug: w3c/DOM-Parsing#29 Bug: w3c/DOM-Parsing#38 Bug: w3c/DOM-Parsing#47 Bug: w3c/DOM-Parsing#48 Bug: w3c/DOM-Parsing#50 Bug: w3c/DOM-Parsing#52 Bug: w3c/DOM-Parsing#59 Bug: w3c/DOM-Parsing#71 Change-Id: I76735c4be1d9738c690417207301f737e3a3c9ff
awesomekling
added a commit
to awesomekling/ladybird
that referenced
this issue
Nov 19, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
awesomekling
added a commit
to awesomekling/ladybird
that referenced
this issue
Nov 19, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
tcl3
pushed a commit
to LadybirdBrowser/ladybird
that referenced
this issue
Nov 19, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
gotlougit
pushed a commit
to gotlougit/ladybird
that referenced
this issue
Nov 21, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
zetslief
pushed a commit
to zetslief/ladybird
that referenced
this issue
Nov 23, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
nico-engels
pushed a commit
to nico-engels/ladybird
that referenced
this issue
Nov 23, 2024
CDATASection inherits from Text, and so it was incorrect for them to claim not to be Text nodes. This fixes at least two WPT subtests. :^) It also exposed a bug in the DOM Parsing and Serialization spec, where we're not told how to serialize CDATASection nodes. Spec bug: w3c/DOM-Parsing#38
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CDATASection nodes returned to the DOM specification in whatwg/dom#295, and browsers still allow them to be serialized. The serialization steps (which are still present in a comment within this specification) should be restored here as well.
The text was updated successfully, but these errors were encountered: