423564 - Bugzilla throwing css errors on console in Firefox because of Opera-specific css

Status: RESOLVED INVALID

(Bugzilla :: User Interface, defect)

Description

[Dave Miller [:justdave]]

From bug 388723 comment 36:

>Note that Firefox now throws tons of warnings in the Error console about these
>two lines:
>
> white-space: -pre-wrap;     /* Opera 4-6 */
> white-space: -o-pre-wrap;   /* Opera 7 */
>
>It seems it doesn't know what to do with them.

Any way to only send that to Opera browsers and get Firefox to ignore it?

Comment 1

[Dave Miller [:justdave]]

I know Internet Explorer has some sort of <!--#if construct or similar that you can mask such things with for IE...

Comment 2

[Frédéric Buclin]

(In reply to comment #1)
> I know Internet Explorer has some sort of <!--#if construct or similar that you
> can mask such things with for IE...
> 

Yes, for instance: http://www.quirksmode.org/css/condcom.html

Comment 3

[Frédéric Buclin]

On the other hand, the Error console in Opera 9.50b shows tons of Firefox-specific css, such as -moz-foo. There is no reason for Bugzilla to be Firefox centric. We should be fair and also find a way to use -moz-foo with Gecko-based browsers only.

Comment 4

[Max Kanat-Alexander]

I don't want to start doing browser-sniffing, though. That can be a maintenance nightmare. We should see if there is some way for the browsers themselves to ignore certain CSS.

Comment 5

[Frédéric Buclin]

(In reply to comment #4)
> I don't want to start doing browser-sniffing, though.

We are not suggesting browser-sniffing, at least using JS. <!--[ifIE]> is a HTML tag seen as a comment by other browsers so that we can pass stuff to IE only. I asked mconnor on IRC, and Fx doesn't have such a feature, unfortunately.

Comment 6

[Dave Garrett]

(In reply to comment #4)
> We should see if there is some way for the browsers themselves to
> ignore certain CSS.

See bug 393757.
Just filed bug 433172.

Comment 7

[Chris Lawson (gone)]

It sounds like this is a WONTFIX (or maybe INVALID, since it's not a bug in Bugzilla), then, since Bugzilla will rely on browsers to do the Right Thing™ when confronted with vendor-specific CSS tags. Bug 433074 covers the current work for Gecko.

Comment 8

[Frédéric Buclin]

For now, this is neither WONTFIX nor INVALID. The CSS code in question is in our CSS files. Unless we can prove there is no better solution than what we have now, this bug remains open.

Comment 9

[Chris Lawson (gone)]

Comment 3 and comment 4 indicate that fixing this within the parameters of a current Firefox build is impossible, and that the "problem" lies elsewhere. I dunno how that's not INVALID or WONTFIX, but sure, doesn't matter to me.

Comment 10

[Max Kanat-Alexander]

Actually, I'd say this is INVALID. That is, it essentially represents a bug in the browser, that it throws warnings about tags that it should just be ignoring. It's true that it still *happens*, but it's not something that we can really do something about, so it's INVALID in the sense that it's "not our bug."