613798 - Comcast's xfinity.com site says it will no longer support my Camino browser

Status: RESOLVED WONTFIX

(Web Compatibility :: Site Reports, defect)

Description

[Jim Emerson]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2010101518 Camino/2.0.5 (like Firefox/3.0.19)
Build Identifier: Camino Version 2.0.5 (1.9.0.19 2010101518)

Comcast's xfinity.com gives me a warning message saying it will no longer support my browser (the latest version of Camino) and urging me to update to IE, Firefox or Safari.  But, of course, Camino is a Mozilla browser like Firefox and Safari. I've complained to xfinity, but hoped you could help.

Reproducible: Always

Steps to Reproduce:
1. go to xfinity.com
2.
3.
Actual Results:  
Got warning message.

Expected Results:  
Should recognize and accept Camino as a valid browser, along with Firefox and Safari.

Comment 1

[Chris Lawson (gone)]

Do you have to have an account to reproduce this? I went to the URL you provided and didn't see any messages about my browser being unsupported at all.

(On an unrelated note, you should update to Camino 2.0.6. It won't solve this issue -- it's likely only Comcast can fix that -- but it will get you a host of security fixes in the Gecko rendering engine.)

Comment 2

[Chris Lawson (gone)]

By the way, definitely keep complaining to Comcast about this. Your voice as a customer is a lot more powerful than ours would be. There are some form letters here that might help you craft a complaint:

http://www-archive.mozilla.org/projects/tech-evangelism/site/tech-letter-en.html

Obviously those are a little dated and need to be customized, but that'll give you a good start.

Comment 3

[Chris Lawson (gone)]

Jim, did you ever yell at Comcast about this? If so, what was their response?

Comment 4

[therube]

This is now affecting SeaMonkey 2.0.x users too.

Used to be that you could click the /I don't want to upgrade - take me to Comcast.net/ link on the page & get on with things, but now that is not working, instead just rolling back to the http://xfinity.comcast.net/browserupgrade/ web page.

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.20pre) Gecko/20110530 SeaMonkey/2.0.15pre

Spoofing the UA, adding "Firefox/4.0" to the UA strings works.
Nonetheless...


"Comcast Blocking SeaMonkey"
http://forums.mozillazine.org/viewtopic.php?f=40&t=2218163


> 00:00:04.306	0.197	625	10143	GET	(Aborted)	text/html	http://xfinity.comcast.net/
> 00:00:04.348	0.128	343	13087	GET	200	text/css	http://por-chr.cimcontent.net/layout/css/compressed/37068-167/home_beta.css
> 00:00:04.351	0.139	571	14549	GET	200	application/javascript	http://xfinity.comcast.net/cimspire/js/cookie.js
> 00:00:04.371	0.060	570	6110	GET	200	application/javascript	http://xfinity.comcast.net/ui/js/lib/browser.js
> 00:00:04.374	0.146	710	0	GET	(Aborted)	NS_BINDING_ABORTED	http://pn1.adserver.yahoo.com/a?bg=ffffff&c=sr&pn=comcast&f=2022780217&p=com-hp&l=NT1&
> 00:00:04.508	0.072	625	4393	GET	200	text/html	http://xfinity.comcast.net/browserupgrade/
> 00:00:04.552	0.075	378	1613	GET	200	text/css	http://por-chr.cimcontent.net/ui/styles/support/browserupgrade/browserupgrade.css?r=37098-12345
> 00:00:04.556	0.096	354	13912	GET	200	text/css	http://por-chr.cimcontent.net/ui/styles/compressed/37051-167/global.css
> 00:00:04.559	0.102	358	1777	GET	200	text/css	http://por-chr.cimcontent.net/ui/styles/compressed/36538/browserupgrade.css
> 00:00:04.563	0.108	342	3817	GET	200	application/javascript	http://por-chr.cimcontent.net/ui/js/compressed/36538-152/browserupgrade.js
>


http://xfinity.comcast.net/ui/js/lib/browser.js looks to be dated June 2, 2011.


(Not an issue in SeaMonkey 2.1 as the UA already includes "Firefox/4.0.1")

Comment 5

[Hallvord R. M. Steen [:hallvors]]

Reproduced with a SeaMonkey 2.0x UA string. 

http://xfinity.comcast.net/ui/js/lib/browser.js has a block for generic "Gecko" detection:

		{
			string: navigator.userAgent,
			subString: "Gecko",
			identity: "Mozilla",
			versionSearch: "rv"
		},

but the function upgradeRedirect() never checks for "Gecko" in the block that detects whether to do the redirect.

Given that this is "fixed" on our side by adding Firefox/xx to the UA string, I think (hope) the importance of this issue is minimal.

Comment 6

[Karl Dubost💡 :karlcow]

RIP Camino. This bug are now WONTFIX.