W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

[Bug 24867] New: [Shadow]: consider supporting :not() in content select

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Feb 2014 18:45:02 +0000
To: public-webapps@w3.org
Message-ID: <bug-24867-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24867

            Bug ID: 24867
           Summary: [Shadow]: consider supporting :not() in content select
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: sjmiles@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14978

"3.6 Satisfying Matching Criteria"

Specifically we have a user with this scenario:

my-figure shadow-root:

  <content select="span:not(.caption)"></content>
  Figure 7: <content select="span.caption"></content>

where his input looks something like this:

  <my-figure>
    <span>Hello World!</span>
    <span class="caption">The caption</span>
  <my-figure>

Without :not() he is forced to: (1) rearrange his input content, (2) rearrange
nodes imperatively, or (3) use CSS to order nodes different at render-time, all
of which are invasive solutions.

I recognize the slippery slope of adding additional abilities to insertion
selectors, but my (admittedly naive) reading of the SELECTORS spec seemed to
imply that supporting :not() may not violate the performance constraints.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 28 February 2014 18:45:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC