mozilla/sanitizer-polyfill

Insufficient feature detection in Chrome 105 Beta

Open

#156 opened on Aug 24, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (8 forks)auto 404
bugenhancementhelp wanted

Repository metrics

Stars
 (76 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently Chrome 105 Beta ships with a basic implmentation of the Sanitizer API, but keeps the .sanitize and .sanitizeFor methods hidden behind the enable-experimental-web-platform-features flag. https://chromestatus.com/feature/5786893650231296

If this flag is not enabled the window.Sanitizer constructor exists, but the object it creates does not have the .sanatize and .sanitizeFor methods. The polyfill currently only checks if window.Sanitizer is a function to decide if it needs to polyfill the API. This means that in Chrome 105 Beta the polyfill is not applied and the .sanitize and .sanitizeFor are missing. Should the final Chrome 105 version ship like this a more complex feature detection is needed.

EDIT: Spell "sanitize" correctly :)

Contributor guide

Research direction
Detect if the Sanitizer object has sanitize and sanitizeFor methods on its prototype; if not, apply the polyfill.
Tech stack
javascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptWeb API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55