New issue
Advanced search Search tips

Issue 851949 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

:matches() selector seems broken in 69.0.3455.0

Reported by vsemozhe...@gmail.com, Jun 12 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3455.0 Safari/537.36

Steps to reproduce the problem:
Compare the next two cases.

What is the expected behavior?
1. Open https://example.org/ in the last dev branch (69.0.3452.0).
2. Enter `document.querySelector('a:matches([href])')` in the console.
3. See the result:

<a href="http://www.iana.org/domains/example">More information...</a>

What went wrong?
1. Open https://example.org/ in the last canary branch (69.0.3455.0).
2. Enter `document.querySelector('a:matches([href])')` in the console.
3. See the error:

Uncaught DOMException: Failed to execute 'querySelector' on 'Document': 'a:matches([href])' is not a valid selector.
    at <anonymous>:1:10

Did this work before? Yes At least the last dev branch (69.0.3452.0)

Chrome version: 69.0.3455.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 30.0.0.113
 

Comment 1 by woxxom@gmail.com, Jun 12 2018

:matches() is enabled only when "Experimental Web Platform features" is enabled in chrome://flags.
Since this selector works for me in 69.0.3455.0 and 69.0.3456.0, I guess you've disabled the flag accidentally.
Labels: Needs-Bisect Needs-Triage-M69
This is true: I was testing some issue on a clean profile and had reset all flags to default (it is a pity we cannot have flags on profiles separately). Sorry for bothering in vain. Please, close.
Labels: -Needs-Bisect Triaged-ET
Status: WontFix (was: Unconfirmed)
As per comment #3, closing the issue as wontFix.

Thanks...!!

Sign in to add a comment