input[type=text] CSS selectors

[Joe Lencioni]

I have some CSS that specifically targets text type input elements
using input[type=text]. Since mod_pagespeed removes the type="text"
from my HTML, these CSS styles are no longer applied. Since CSS does
not allow for a does-not-equal attribute selector (input[type!=radio|
checkbox|submit|etc]) and I don't want to target all input elements,
what is the best way to target these types of inputs? Should I give
them a class of text or is there a way to specifically disable this
particular optimization that mod_pagespeed performs without disabling
an entire category of optimizations?

Running mod_pagespeed 0.9.8.1-215.

[Joshua Marantz]

Can you given an HTML fragment or a URL?

mod_pagespeed should not take your working HTML/CSS and make it stop working.  If you give a working example that mod_pagespeed breaks, then we will fix the problem ASAP and also send you a temporary workaround.

Thanks!

-Josh

[Shawn Ligocki]

This is a known risk of elide_attributes that Matthew found. We need to add this to the elide_attributes documentation.

I think Matthew found a way to edit your CSS to fix this.

-Shawn

[Matthew Steele]

Yes, this is a known issue with elide_attributes. You can, of course,
simply turn that single filter off in your Apache configuration,
using:

ModPagespeedDisableFilters elide_attributes

If you'd prefer to keep it, however, I believe you can work around the
problem by changing your CSS by replacing rules such as:

input[type="text"] { ... }

with:

input:not([type]), input[type="text"] { ... }

This will match if type="text", or if the type attribute is not present at all.

[Joe Lencioni]

Awesome guys, thanks for the fast response!

On Nov 18, 1:01 pm, Matthew Steele <mdste...@google.com> wrote:
> Yes, this is a known issue with elide_attributes.  You can, of course,
> simply turn that single filter off in your Apache configuration,
> using:
>
>   ModPagespeedDisableFilters elide_attributes
>
> If you'd prefer to keep it, however, I believe you can work around the
> problem by changing your CSS by replacing rules such as:
>
>   input[type="text"] { ... }
>
> with:
>
>   input:not([type]), input[type="text"] { ... }
>
> This will match if type="text", or if the type attribute is not present at all.
>
>
>
>
>
>
>
> On Thu, Nov 18, 2010 at 1:43 PM, Shawn Ligocki <sligo...@google.com> wrote:
> > This is a known risk of elide_attributes that Matthew found. We need to add
> > this to the elide_attributes documentation.
> > I think Matthew found a way to edit your CSS to fix this.
>
> > -Shawn
>

> > On Thu, Nov 18, 2010 at 1:04 PM, Joshua Marantz <jmara...@google.com> wrote:
>
> >> Can you given an HTML fragment or a URL?
> >> mod_pagespeed should not take your working HTML/CSS and make it stop
> >> working.  If you give a working example that mod_pagespeed breaks, then we
> >> will fix the problem ASAP and also send you a temporary workaround.
> >> Thanks!
> >> -Josh
>

> >> On Thu, Nov 18, 2010 at 11:47 AM, Joe Lencioni <joe.lenci...@gmail.com>