Closed Bug 1478956 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 12202 - Fix test case which relied on outdated Name/QName production

Categories

(Core :: DOM: Core & HTML, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12202 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/12202
Details from upstream follow.

C. Scott Ananian <cscott@cscott.net> wrote:
>  Fix test case which relied on outdated Name/QName production
>  
>  The latest version of the DOM spec references the Name and QName productions from XML (https://dom.spec.whatwg.org/#validate).  In errata 9 from XML 1.0 these productions were changed to be much more inclusive ( https://www.w3.org/XML/xml-V10-4e-errata#E09 ) which means these old test cases are overly restrictive.
>  Changed to mark \u0BC6 as valid in a qname, and added a new test case using \u037E for the invalid case.
Component: web-platform-tests → DOM
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Failed to get results from try push
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5f88e8a5b484
[wpt PR 12202] - Fix test case which relied on outdated Name/QName production, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/502e41243576
[wpt PR 12202] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/5f88e8a5b484
https://hg.mozilla.org/mozilla-central/rev/502e41243576
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.