Investigate `Event.path()` usage
Categories
(Web Compatibility :: Tooling & Investigations, task)
Tracking
(Webcompat Priority:P3)
Webcompat Priority | P3 |
People
(Reporter: denschub, Unassigned)
References
(Blocks 2 open bugs)
Details
Relying on the non-standard Shadow DOM Event.path()
broke YouTube's search bar in bug 1697551.
James found https://www.chromestatus.com/metrics/feature/timeline/popularity/345, which is concerning as that shows Event.path()
is used in ~16% of all Chrome page loads.
We should investigate what that usage is, if it's real usage, and if it could be a win for us to alias path()
to composedPath()
(and how doing so could potentially backfire..)
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
The usage pattern is now 18%. But in the discussions on the previous link, they mention that maybe the usecounter counting event.Path doesn't know how to distinguish. event.path
from event.path || event.composedPath()
so it's very hard to decipher if it would actually break something for them. What they intend to do is to dig into HTTP Archive.
From my own digging into GitHub there are a lot of cases like this event.path || event.composedPath()
Description
•