Skip to content
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

Open
Zirro opened this issue Dec 4, 2018 · 1 comment
Open

Restore serialization of CDATASection nodes #38

Zirro opened this issue Dec 4, 2018 · 1 comment

Comments

@Zirro
Copy link

Zirro commented Dec 4, 2018

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.

@cscott
Copy link

cscott commented Jul 2, 2021

The serialization steps were in a comment which was removed, but they can still be found at

<!-- Removing CDATA Serialization steps as this interface type is removed from DOM4

(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 ]]> ? That wasn't in the previous commented-out version of the spec, but it seems consistent.

wmfgerrit pushed a commit to wikimedia/mediawiki-libs-Dodo that referenced this issue Jul 3, 2021
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
Projects
None yet
Development

No branches or pull requests

3 participants