so why not use a Javascript solution?
As a horrible understatement, because I'm not very good at javascript ;)
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on
Is there any valid way make firefox (well, gecko in general)
ignore a rule
*|* selector {property:value}
pretty sure mozilla is the only browser to apply this rule from memory
YMMV and you probably want to check KHTML browsers.
kind regards
Terrence Wood.
, 29 October 2005 8:17 p.m.
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Firefox filter?
I would be concerned about a bug only showing up in Firefox, I believe
that hiding something from Firefox is not the way to go, but rather,
make it right in Firefox and then worry about the others.
Usually
I would be concerned about a bug only showing up in Firefox, I believe
that hiding something from Firefox is not the way to go, but rather,
make it right in Firefox and then worry about the others.
Usually I'd agree. But in this case, that won't work. :(
Kenny Graham wrote:
I would be concerned about a bug only showing up in Firefox, I
believe that hiding something from Firefox is not the way to go,
but rather, make it right in Firefox and then worry about the
others.
Usually I'd agree. But in this case, that won't work. :(
I don't agree
I'm also not sure how browsers are supposed to handle a non-repeating
animated gif as on-hover background, so I don't know what's correct
behavior here.
I'm not sure what the correct way is either, but regardless, I don't
code to firefox or any other browser first. I code to standards
first.
On 10/30/05, Kenny Graham [EMAIL PROTECTED] wrote:
So back to the original question, is there any way to serve a rule
only to firefox (or only to non-firefox) without invalidating the css?
Heh, server-side browser sniffing? ;-)
/flamebait
Josh
Kenny Graham wrote:
So back to the original question, is there any way to serve a rule
only to firefox (or only to non-firefox) without invalidating the
css?
Use the http://www.gunlaug.no/contents/styles/target-browser.css
and delete the @import for Opera 9+ on top (until the validator
Joshua Street wrote:
On 10/30/05, Kenny Graham [EMAIL PROTECTED] wrote:
So back to the original question, is there any way to serve a rule
only to firefox (or only to non-firefox) without invalidating the css?
Heh, server-side browser sniffing? ;-)
/flamebait
Seriously, why is this
Mark Harris wrote:
Seriously, why is this flamebait. I suggested this in another thread a
couple of days ago. Is there a problem I'm not aware of with server-side
sniffing?
Any user agent sniffing (client- or server-side) has two main issues:
- to be pedantic, it goes against the idea of a
On 10/30/05, Mark Harris [EMAIL PROTECTED] wrote:
Seriously, why is this flamebait. I suggested this in another thread a
couple of days ago. Is there a problem I'm not aware of with server-side
sniffing?
Mm, well... it's not really a problem if it's properly maintained.
But, seeing as many
I'm also not sure how browsers are supposed to handle a non-repeating
animated gif as on-hover background, so I don't know what's correct
behavior here.
I'm not sure what the correct way is either, but regardless, I don't
code to firefox or any other browser first. I code to standards
I make it a point to test in Firefox first, since historically it is
nearly free of rendering bugs. IE and Opera come next, once the 3 are
behaving, you should be in good shape.
I would be concerned about a bug only showing up in Firefox, I believe
that hiding something from Firefox is not
13 matches
Mail list logo
