| Summary: | Web Inspector: Support Custom Formatters | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Compton <desk> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, karlcow, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Daniel Compton
2023-11-15 18:13:51 PST
I had a quick chat with dcrousso on WebKit Slack about this (https://webkit.slack.com/archives/CU65DUH7F/p1700101038513779) dcrousso: as far as this particular feature, i haven't looked at custom formatters in a while, but generally speaking we've avoided things that expose whether Web Inspector is open and i think this may violate that so that's probably be the first thing that needs to be addressed dcrousso: if we can figure out a solution to that then anyone is welcome to create a PR and ask for reviews Daniel Compton: Would custom formatters being disabled by default be a mitigating factor? dcrousso: possibly? I'm very hesitant to expose anything that lets the page detect Web Inspector so directly (even if disabled by default). The main concern being the page doing some sort of denial-of-service if Web Inspector is opened and i'm not sure if developers would think/know that custom formatters is a detection mechanism in order to disable it. If it's something that has to be enabled each session i'm less concerned about a developer forgetting about it being enabled, but i also feel like the experience of that might suck, but if you're ok with that then i think it's perhaps worth exploring/prototyping 🙂 Daniel Compton: Yeah, enabling it every session wouldn't be much fun. I'll have a look at the spec and see what the options are. |