forked from WebKit/WebKit-http
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
XMLSerializer.serializeToString() doesn't properly escape \n, \n and \t
https://bugs.webkit.org/show_bug.cgi?id=227844 Reviewed by Darin Adler. LayoutTests/imported/w3c: Rebaseline WPT test now that one more subtest is passing. * web-platform-tests/domparsing/XMLSerializer-serializeToString-expected.txt: Source/WebCore: XMLSerializer.serializeToString() doesn't properly escape \n, \n and \t. This is causing the "check XMLSerializer.serializeToString escapes attribute values for roundtripping" subtest to fail in WebKit on: http://wpt.live/domparsing/XMLSerializer-serializeToString.html Chrome and Firefox both escape these and pass this WPT subtest. The specification does not indicate we should escape those: - https://w3c.github.io/DOM-Parsing/#dfn-serializing-an-attribute-value But there is an open bug about this: - w3c/DOM-Parsing#59 No new tests, rebaselined existing test. * editing/MarkupAccumulator.cpp: (WebCore::elementCannotHaveEndTag): * editing/MarkupAccumulator.h: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@279815 268f45cc-cd09-0410-ab3c-d52691b4dbfc
- Loading branch information
1 parent
bab137f
commit a8eeda9
Showing
5 changed files
with
53 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,14 @@ | ||
2021-07-11 Chris Dumez <[email protected]> | ||
|
||
XMLSerializer.serializeToString() doesn't properly escape \n, \n and \t | ||
https://bugs.webkit.org/show_bug.cgi?id=227844 | ||
|
||
Reviewed by Darin Adler. | ||
|
||
Rebaseline WPT test now that one more subtest is passing. | ||
|
||
* web-platform-tests/domparsing/XMLSerializer-serializeToString-expected.txt: | ||
|
||
2021-07-10 Chris Dumez <[email protected]> | ||
|
||
document.readyState should be "complete" after calling DOMParser.parseFromString() | ||
|
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,28 @@ | ||
2021-07-11 Chris Dumez <[email protected]> | ||
|
||
XMLSerializer.serializeToString() doesn't properly escape \n, \n and \t | ||
https://bugs.webkit.org/show_bug.cgi?id=227844 | ||
|
||
Reviewed by Darin Adler. | ||
|
||
XMLSerializer.serializeToString() doesn't properly escape \n, \n and \t. | ||
|
||
This is causing the "check XMLSerializer.serializeToString escapes attribute values for roundtripping" subtest to fail in WebKit on: | ||
http://wpt.live/domparsing/XMLSerializer-serializeToString.html | ||
|
||
Chrome and Firefox both escape these and pass this WPT subtest. | ||
|
||
The specification does not indicate we should escape those: | ||
- https://w3c.github.io/DOM-Parsing/#dfn-serializing-an-attribute-value | ||
But there is an open bug about this: | ||
- https://github.com/w3c/DOM-Parsing/issues/59 | ||
|
||
No new tests, rebaselined existing test. | ||
|
||
* editing/MarkupAccumulator.cpp: | ||
(WebCore::elementCannotHaveEndTag): | ||
* editing/MarkupAccumulator.h: | ||
|
||
2021-07-10 Chris Dumez <[email protected]> | ||
|
||
document.readyState should be "complete" after calling DOMParser.parseFromString() | ||
|
This file contains 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
This file contains 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