Open Bug 1331793 Opened 5 years ago Updated 2 months ago

Consider not throwing on querySelector("::-webkit-scrollbar")


(Core :: DOM: CSS Object Model, defect, P3)




Webcompat Priority revisit
Tracking Status
firefox53 --- affected


(Reporter: wisniewskit, Unassigned)



(Whiteboard: [webcompat])

We received a report on which boiled down to site navigation being partly broken because document.querySelector("::-webkit-scrollbar") throws an error:

>SyntaxError: '::-webkit-scrollbar' is not a valid selector

In this case, it was throwing in a commercial web library by 3D Issue, so it's likely that other sites are also going to have problems with this (given that this is a pseudo-element that works in Chrome/WebKit).

Perhaps we ought to not throw in this case, but simply return no elements for that pseudo-element?
I'd be hesitant to do this based on a single report, since this is a mechanism that can be used to tell whether a selector is actually supported.
Priority: -- → P3
See Also: → 1424106

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Webcompat Priority: --- → ?

See bug 1547409. Migrating whiteboard priority tags to program flags.

Webcompat Priority: ? → revisit
You need to log in before you can comment on or make changes to this bug.