Closed Bug 1837613 Opened 1 years ago Closed 1 year ago

[wpt-sync] Sync PR 40473 - Fix invalid HTML: /> syntax on non-void elements

Categories

(Core :: DOM: Security, task, P4)

task

Tracking

()

RESOLVED FIXED
116 Branch
Tracking Status
firefox116 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

zcorpan <zcorpan@gmail.com> wrote:

Fix invalid HTML: /> syntax on non-void elements

In VSCode, I searched for

<(a|abbr|article|audio|b|bdi|bdo|blockquote|body|button|canvas|caption|cite|code|colgroup|data|datalist|dd|del|details|dfn|dialog|div|dl|dt|em|fieldset|figcaption|figure|footer|form|h[1-6]|head|header|html|i|iframe|ins|kbd|label|legend|li|main|map|mark|menu|meter|nav|noscript|object|ol|optgroup|option|output|p|picture|pre|progress|q|rp|rt|ruby|s|samp|script|search|section|select|slot|small|span|strong|style|sub|summary|sup|table|tbody|td|template|textarea|tfoot|th|thead|time|title|tr|u|ul|var|video|wbr)(\s+[^>]+)?\s*/>

and replaced with

<$1$2></$1>

(with some manual fixups)

Files to include: *.html, *.htm
Files to exclude: dom/nodes/, domparsing/, quirks/, conformance-checkers/, acid/ (these are testing XML parsing, except Acid3 which has pseudo-markup in comments)

PR 40473 applied with additional changes from upstream: 93898208a9ae611db97d4a5c8ebf6adf9e3970d3, 09f32d87cded8a1e4a6cbb7cf64cea9e6239dcca
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a4cce9662000 [wpt PR 40473] - Fix invalid HTML: /> syntax on non-void elements, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.