ISSUE-320: Profile :matches() / :not() for fast vs. complete implementation

Profile :matches() / :not() for fast vs. complete implementation

State:

RAISED

Product:

Selectors Level 4

Raised by:

Elika Etemad

Opened on:

2013-04-04

Description:

People keep being confused about :matches() and :not()'s intention to allow full complex selectors. The only reason they're not allowed is perf, so let's just make two profiles for Selectors and let things like Selectors API and PDF processors implement the full version.

Related Actions Items:

No related actions

Related emails:

1. Re: CSS-ISSUE-320: Profile :matches() / :not() for fast vs. complete implementation [Selectors Level 4] (from jackalmage@gmail.com on 2013-04-22)
2. RE: CSS-ISSUE-320: Profile :matches() / :not() for fast vs. complete implementation [Selectors Level 4] (from francois.remy.dev@outlook.com on 2013-04-22)
3. Re: CSS-ISSUE-320: Profile :matches() / :not() for fast vs. complete implementation [Selectors Level 4] (from dbaron@dbaron.org on 2013-04-22)
4. Re: [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-17)
5. [CSSWG] Minutes Telecon 2013-04-10 (from fantasai.lists@inkedblade.net on 2013-04-10)
6. Re: [selectors4] Open issues (from simon.sapin@exyr.org on 2013-04-09)
7. [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-08)
8. CSS-ISSUE-320: Profile :matches() / :not() for fast vs. complete implementation [Selectors Level 4] (from sysbot+tracker@w3.org on 2013-04-04)

Related notes:

No additional notes.

Display change log