Closed Bug 1331793 Opened 7 years ago Closed 2 years ago

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

Categories

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

Product:
Core
Component:
DOM: CSS Object Model
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
Webcompat Priority revisit
Tracking Flags:
Tracking Status
firefox53 --- affected

People

(Reporter: wisniewskit, Unassigned)

References

Details

(Whiteboard: [webcompat]) 

We received a report on webcompat.com 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

We don't throw on unknown webkit pseudos

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.