Hello devtools-dev,
The Edge team has been approached by a couple of teams to bring usage error adorners into Chromium DevTools. (I'll just be straightforward: in Edge, they are squiggles). We were approached by a couple of teams who are working on DOM-related features (<select>,
accessibility) who wanted to leverage Edge's squiggles to express to a developer, "You're doing this wrong."
We have a larger overall vision for this project, briefly talked about in
this document which will eventually link up to all of the explainers. But the nearer-term project - intent to prototype - is
this one, which is: create a new set of DOM-linked Issues, and enable Issues to
adorn DOM nodes in the Elements tool.
We are open to using different adorners than squiggles, although I've considered a couple alternatives. I think the best way to approach this is to stick to explicit error cases (incorrect immediate children of <select> and incorrect attribute combinations
for accessibility). I'm reluctant to add more options, but I think these would be sufficient to start. It is probably also sufficient for us to being collecting histograms on the frequency with which these or "warning-level" issues would be present.
We're likely to start investing on this shortly after the first of the year, but we may begin landing new issues ahead of time.
Thanks,
Rob Paveza
|
DOM Element Semantic Error Adorners Instructions for Googlers: Design documents are intended to be public, so create them with your Chromium account. Move them to the Design Documents folder of the Chromium DevTools team drive (permissions are automatically
applied). Be sure to update the aut...
|
|
Contextual DOM Hints in DevTools rob.p...@microsoft.com - November 1, 2024 Status: Exploratory This document is attempting to cast a unifying vision for three new features. We believe these features together afford a significant value proposition, but individually
are too large to all be explo...
|