545769 - is the Personas rollover feature on First Run broken?

Status: RESOLVED WORKSFORME

(www.mozilla.org :: General, defect)

Description

[John Slater]

I'm getting some reports that the Personas rollover feature on the First Run page may not be working. 

Here's a quote from cbeard:
"it looks like the persona-preview on mouseover doesn't seem to work. odd in that it works for me with https (https://www.mozilla.com/en-US/firefox/3.6/firstrun/) but not http

also, i don't see the add-on promo with the http version
i also flushed my cache and tried a unique url to see if it was an edge serving issue
http://www.mozilla.com/en-US/firefox/3.6/firstrun/?blah"

and another quote from Pascal:
"This seems to be a weird bug - Sean Martell just reported that the whole mouse-over thing never worked on one profile, but works perfectly well on another profile he has..."

For the record, the rollover works fine for me on http and https. But, it'd be great to investigate this further.

Comment 1

[Alex Buchanan [:abuchanan]]

Works for me.

Comment 2

[John Slater]

Is anyone else having this problem?

Comment 3

[Pascal Finette [:pfinette]]

Sean Martell can definitely replicate this with one of his Fx profiles. It works fine in a different profile.

Comment 4

[John Slater]

Copying Sean...

Comment 5

[Sean Martell]

Hey, yes for some reason my default profile doesn't work with the rollover, but if I create a new profile, it works.

Perhaps others who have the issue should test and create a new profile to check to see if that fixes it for them as well?

Not sure of the actual problem, and my method is not a solution, but I did notice that it worked.

Comment 6

[Stephen Donner [:stephend] Not actively reading bugmail]

I can't reproduce this in neither current profiles nor a clean one, but a couple possibilities exist:

A) Is it possible that our CDN (EdgeCast) was in the process of origin pull (where it pulls and caches our CSS, images, and JS), and stored the old version and the ETag [1] was wrong?

B) The other possibility is that our expires headers were wrong

Alex and Ryan would have a better idea than I as to whether either would be probable causes; Ryan, you're the guy who knows the most about our YSlow! support on Mozilla.com; any ideas?

Can those whom still experience this do some minor debugging through Live HTTP Headers and/or Firebug?

Comment 7

[Stephen Donner [:stephend] Not actively reading bugmail]

[1] http://en.wikipedia.org/wiki/HTTP_ETag

Comment 8

[Ryan Doherty (:rdoherty)]

(In reply to comment #6)
> A) Is it possible that our CDN (EdgeCast) was in the process of origin pull
> (where it pulls and caches our CSS, images, and JS), and stored the old version
> and the ETag [1] was wrong?

The firstrun page on getpersonas.com doesn't use any far-future expires header caching, so the files can't be cached. They get refreshed pretty often (probably every min or less).

> B) The other possibility is that our expires headers were wrong

Same as A, no expires headers = no caching.

The promos for the firstrun page aren't related to getpersonas.com, that can be a separate bug.

Sean: what add-ons are installed in the profile that doesn't work? Adblock Plus has been known to block js on getpersonas.com

Comment 9

[Kohei Yoshino [:kohei]]

Some users have reported the same issue on the MozillaZine.jp forum. He/she resolved this by creating a new profile and coping its permissions.sqlite onto the default profile.