Closed
Bug 1764254
Opened 2 years ago
Closed 2 years ago
[sanitizer] Disable `sanitizeFor`
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: freddy, Assigned: freddy)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 1 obsolete file)
We've reached agreement that sanitizeFor
should be deferred to a future version (See https://github.com/WICG/sanitizer-api/issues/128).
Given that sanitizeFor
as its currently implemented is not interoperable, so let's remove it completely.
Assignee | ||
Comment 1•2 years ago
|
||
Pushed by fbraun@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e5e39bcd8a56 remove Sanitizer.sanitizeFor r=hsivonen
Assignee | ||
Comment 3•2 years ago
|
||
Comment 4•2 years ago
|
||
Backed out for causing wpt failures on sanitizer-config.https.tentative.html
Failure line(s): TEST-UNEXPECTED-FAIL | /sanitizer-api/sanitizer-config.https.tentative.html | SanitizerAPI: allowElements modify is okay. - sanitizer.sanitizeFor is not a function
Flags: needinfo?(fbraun)
Updated•2 years ago
|
Severity: -- → S4
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Updated•2 years ago
|
Attachment #9271874 -
Attachment is obsolete: true
Pushed by fbraun@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cc69fdfbecfe remove Sanitizer.sanitizeFor r=hsivonen
Comment 7•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•