See bug 776376 comment 19 and FYI: the webmail of aol.com also seems to identify "Firefox the wrong way" and does show a old version of the interface only. Overrided the useragent string to ... Gecko/20120429 ... and found the new interface appearing. Reported the user agent issue to AOL. Waiting for response now.

This will be an easy fix for AOL. The question is whether we can reach them to get them fix it before it hits users. If they only react once it has hit users, then the question is how severe this bug is, i.e.: how much inferior is this old version of the interface?

(In reply to Dão Gottwald [:dao] from comment #1) > This will be an easy fix for AOL. The question is whether we can reach them > to get them fix it before it hits users. I think the real question is whether they can get a fix out in the next couple of weeks, since after that, backing out bug 588909 to may cause other server-side web regressions later in the cycle. > If they only react once it has hit > users, then the question is how severe this bug is, i.e.: how much inferior > is this old version of the interface? Does this UA change have so much value in the short-term that we'd consider taking any visible regression like this on a major web property?

(In reply to Alex Keybl [:akeybl] from comment #2) > Does this UA change have so much value in the short-term that we'd consider > taking any visible regression like this on a major web property? Since it took months for this bug to be reported, I expect the regression to be negligible. However, backing out bug 588909 from aurora surely is a reasonable option as well.

(In reply to Dão Gottwald [:dao] from comment #3) > (In reply to Alex Keybl [:akeybl] from comment #2) > > Does this UA change have so much value in the short-term that we'd consider > > taking any visible regression like this on a major web property? > > Since it took months for this bug to be reported, I expect the regression to > be negligible. However, backing out bug 588909 from aurora surely is a > reasonable option as well. Instead of keeping changing the UA string back and forth for all sites thereby giving all sites the opportunity to sniff for the parts we are trying to remove, I suggest we send a different UA string for mail.aol.com only. Chrome has done that sort of thing e.g. for Yahoo! Mail, and experience shows that they've been able to remove such hacks after some time, so we shouldn't be afraid of such hacks becoming too much of a maintenance burden.

(In reply to Henri Sivonen (:hsivonen) from comment #4) > (In reply to Dão Gottwald [:dao] from comment #3) > > (In reply to Alex Keybl [:akeybl] from comment #2) > > > Does this UA change have so much value in the short-term that we'd consider > > > taking any visible regression like this on a major web property? > > > > Since it took months for this bug to be reported, I expect the regression to > > be negligible. However, backing out bug 588909 from aurora surely is a > > reasonable option as well. > > Instead of keeping changing the UA string back and forth for all sites > thereby giving all sites the opportunity to sniff for the parts we are > trying to remove, I suggest we send a different UA string for mail.aol.com > only. > > Chrome has done that sort of thing e.g. for Yahoo! Mail, and experience > shows that they've been able to remove such hacks after some time, so we > shouldn't be afraid of such hacks becoming too much of a maintenance burden. See bug 782453.

Firefox 17 isn't affected by this anymore since bug 782453 landed there.

j.j.: have you heard anything back from AOL? What contact methods did you use to notify them of this problem? Gerv

I described the problem to AOL Mail Support and got the standard answer first telling me to reset browser settings (cookies, cache, history, ...) and use default browser. Replied to that with a step by step explanation (Gerv, forwarded to you) to reproduce the problem. From: AOL Mail Team <AOLMailQuestions@aol.com> [...] We always appreciate customers who take the time to give us their feedback. I'll pass what you've said onto our management team. [...] Since then, did not hear anything back (not expecting any response).

(In reply to Gervase Markham [:gerv] from comment #7) > j.j.: have you heard anything back from AOL? (I just cited Bruno Marsal's comment)

Really don't like modifying UA strings per site as a general rule, and think we should avoid things like bug 782453 that is caused by sniffing for something we change, as it defeats the point of the change we made. I hadn't seen this issue before, and will raise it with Aol, as well. Going through their general support rarely gets much traction.

Just tried again setting general.useragent.override with "Mozilla/5.0 (Windows NT x.y; rv:10.0) Gecko/10.0 Firefox/10.0" and was successfully logging into the new AOL Mail UI. Seems they fixed that. Can somebody confirm?

(In reply to Kev [:kev] Needham from comment #10) > Really don't like modifying UA strings per site as a general rule, and think > we should avoid things like bug 782453 that is caused by sniffing for > something we change, as it defeats the point of the change we made. Undoing the change for a handful of sites out of billions certainly doesn't defeat the point of the change.

(In reply to Bruno Marsal (Bullja) from comment #11) > Just tried again setting general.useragent.override with "Mozilla/5.0 > (Windows NT x.y; rv:10.0) Gecko/10.0 Firefox/10.0" and was successfully > logging into the new AOL Mail UI. Seems they fixed that. > > Can somebody confirm? general.useragent.override isn't going to make a difference, the preference in question is general.useragent.override.aol.com. That said, it indeed seems like it's fixed.

That's your opinion. I'll shut up moving forward. (In reply to Dão Gottwald [:dao] from comment #12) > Undoing the change for a handful of sites out of billions certainly doesn't > defeat the point of the change.

Why is this bug resolved? The problem is still present. The bug can be resolved when AOL has fixed their site and we can remove the preference which mitigates the problem. Adding a site to an override list is not a "fix", it's a temporary mitigation. Gerv

(In reply to Gervase Markham [:gerv] from comment #15) > Why is this bug resolved? Because AOL apparently fixed the problem.

Oh, awesome! Sorry, I didn't notice that. So can we remove the entry from the UA override list, then? Gerv