Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha - Desktop Packager Dev Team jarrednicholls's Avatar
    Join Date
    Mar 2007
    Location
    Frederick, MD
    Posts
    1,747
    Vote Rating
    7
    jarrednicholls will become famous soon enough jarrednicholls will become famous soon enough

      0  

    Default [OPEN-179][3.0.0] CSS3 Selector Parse Bug

    [OPEN-179][3.0.0] CSS3 Selector Parse Bug


    CSS3 pseudo-class selectors such as :not() do not parse correctly when doing "or" selectors.

    For example, this parses correctly:

    Code:
    .required:not(input.required)
    but this does not parse correctly

    Code:
    .required:not(input.required, select.required)
    CSS3 pseudo-classes can absolutely have "or" selectors (comma-separated selectors) as arguments to the pseudo-classes. I would write this up as a bug and take a look at enhancing DomQuery to solve that issue.

    Thanks.

  2. #2
    Sencha - Ext JS Dev Team Animal's Avatar
    Join Date
    Mar 2007
    Location
    Notts/Redwood City
    Posts
    30,507
    Vote Rating
    56
    Animal has a spectacular aura about Animal has a spectacular aura about Animal has a spectacular aura about

      0  

    Default


    As a workaround you could add your own pseudo class selector to the DomQuery class, so you could use

    Code:
    .required:notinputorselect
    Here's an example of adding a pseudo: http://extjs.com/forum/showthread.ph...378#post374378

    Just until they fix it.

Thread Participants: 1