The use counter for these is still pretty high, but maybe with research it may turn out we can remove it. It would be very useful if there was a prioritized list. I feel like triaging these bugs increases toil without moving the needle on compatibility.

The use counters:
https://www.chromestatus.com/metrics/feature/timeline/popularity/357
https://www.chromestatus.com/metrics/feature/timeline/popularity/358

Because of scripts enumerating all attributes on window these use counters are almost certainly over-counting by a large factor, so the absolute numbers aren't of much use. The ~0.06% difference between the two is interesting, though, it could mean that defaultStatus is used at least on ~0.06% of page loads.

I believe that only httparchive analysis could move this issue forward.

Once we have finished triaging non-standard interfaces, attributes and methods in issue  674593 I'd like to make per-component or per-team lists, where we could indicate which (if any) are likely to be real-world compat issues worth investigating first.

In the meantime, we don't expect a large number of these issues to get immediate traction, and to be fixed mostly on a "this seems fun/easy" basis, like  issue 692665 .

Bulk disowning per sshruthi's email about bug triage best practices.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot