609823 - @font-face in a background tab is not applied until the tab gets focus

Status: RESOLVED INVALID

(Core :: Layout: Text and Fonts, defect)

Description

[Jeff Balogh (:jbalogh)]

1. Open http://docs.pylonshq.com/ in a background tab.
2. Wait until the page is loaded and ready.
3. Switch to the tab.
4. Observe the flash of unstyled text as @font-face kicks in.

The @font-face comes from http://fonts.googleapis.com/css?family=Nobile:regular,italic,bold,bolditalic&subset=latin

I'm running Minefield on the Mac. (Built from http://hg.mozilla.org/mozilla-central/rev/0c4fb639c49e)

Comment 1

[Boris Zbarsky [:bzbarsky]]

This seems to work for me with the 2010-10-31 build (on Mac)....

Comment 2

[Jeff Balogh (:jbalogh)]

Tested on a clean profile and I couldn't reproduce. Turns out this is (not that surprisingly) an issue with Firebug.

Do we do anything special with Firebug bugs that make Firefox look bad besides filing them in the Firebug tracker?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Nope.  Sadly.

Did you actually have Firebug active?

I'd really love to know how Firebug manages to trigger this problem...

Comment 4

[John J. Barton]

Jeff, first use Firebug Status bar icon right click clear all activation. Then please try these combinations:

1) Your original steps to reproduce,
2) Turn on firebug for the background tab, retest
3) Turn firebug off for the background tab (red button upper right) and on for the other tab, retest
4) Turn firebug off for both tabs, retest.

Based on which of these show your issue, we can narrow down the problem.

Comment 5

[Jeff Balogh (:jbalogh)]

(In reply to comment #3) 
> Did you actually have Firebug active?

I don't have the Firebug console open, so I think it's in a semi-inactive state.  The HTML, CSS, and DOM panels are available when I open Firebug.

Filed http://code.google.com/p/fbug/issues/detail?id=3621.

Comment 6

[Boris Zbarsky [:bzbarsky]]

> I don't have the Firebug console open

That doesn't matter.  What matters is what color the bug is....

Let's follow up with a response to comment 4 over in the firebug bug?