Description of problem: Visiting (as one example) the product web page at newegg.com: http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070 The price and "add to cart" button that is normally displayed in a box near the center of the page does not show up. Mail thread here may have more details: http://lists.fedoraproject.org/pipermail/test/2011-November/104250.html One weird thing which may be relevant - if you run firefox as root, the price does appear, but running as ordinary user, it does not. On fedora 15, the problem does not show up - the prices are visible. Version-Release number of selected component (if applicable): firefox-7.0.1-3.f16.x86_64 How reproducible: 100% for all the individual product pages I visited on newegg.com Steps to Reproduce: 1.see above 2. 3. Actual results: No price or add to cart button Expected results: Price and add to cart button Additional info: A google search for this problem turned up a user who had javascript turned off and that was the cause, but I do not have javascript disabled.
Created attachment 531552 [details] screenshot of broken web page on fedora 16
Created attachment 531553 [details] screenshot of working web page on fedora 15
No problem here - firefox-7.0.1-3.fc16.i686. Note that I have a 32-bit system. My home directory was created from scratch for F16.
I see this bug on F14, with firefox-3.6.23-1.fc14.x86_64. No change when I disable my only two add-ons (adblock plus 1.3.10 and Flashblock 1.5.15.1, with a browser restart). Haven't tried it as root. nouveau driver here, with: 05:00.0 VGA compatible controller: nVidia Corporation NV43GL [Quadro FX 540] (rev a2) In a WinXP VM, same firefox 3.6.23 with same add-ins, works OK.
Works for me. F16 with updates. Also nouveau driver. Smolt profile: http://www.smolts.org/client/show/pub_28430bb9-a948-43ba-b8fa-4e68d54dc9e2
OK, this has officially gotten really weird. I tracked down the javascript that shows the price, and it is the one chunk of web page loaded from content.newegg.com. Attempting to access that as a web page says it can't resolve content.newegg.com, but using "host" to resolve it works fine: [tweety@tomh ~]$ wget http://content.newegg.com/LandingPage/ItemInfo4ProductDetail.aspx?Item=N82E16819115070 --2011-11-03 15:46:06-- http://content.newegg.com/LandingPage/ItemInfo4ProductDetail.aspx?Item=N82E16819115070 Resolving content.newegg.com... failed: Name or service not known. wget: unable to resolve host address “content.newegg.com” [tweety@tomh ~]$ host content.newegg.com content.newegg.com has address 216.52.208.152 [tweety@tomh ~]$ Why can "host" find it, but firefox and wget can't? And if I do this, it works and even saves off a file where I can find stuff like the price: [tweety@tomh ~]$ wget http://216.52.208.152/LandingPage/ItemInfo4ProductDetail.aspx?Item=N82E16819115070 --2011-11-03 15:50:43-- http://216.52.208.152/LandingPage/ItemInfo4ProductDetail.aspx?Item=N82E16819115070 Connecting to 216.52.208.152:80... connected. HTTP request sent, awaiting response... 200 OK Cookie coming from 216.52.208.152 attempted to set domain to 216.52.208.152 Length: 3725 (3.6K) [text/javascript] Saving to: “ItemInfo4ProductDetail.aspx?Item=N82E16819115070” 100%[======================================>] 3,725 --.-K/s in 0s 2011-11-03 15:50:43 (132 MB/s) - “ItemInfo4ProductDetail.aspx?Item=N82E16819115070” saved [3725/3725]
Ah-HA! On my fedora15 partition, I have my trusty original home directory where long ago I set the about:config parameter network.dns.disableIPv6 to "true". On fedora 16 I have a fresh install with the default "false" value. When I set it to "true", the prices start appearing again. So this is really an IPv6 versus v4 issue (though why it only seems to affect content.newegg.com and nothing else, I have no idea).
I can confirm on F14, though I can't explain why it works. Reverting to firefox-3.6.10-1.fc14.x86_64 & xulrunner-1.9.2.10-1.fc14.1.x86_64 still showed the problem. Changing network.dns.disableIPv6 from "default" to "true" allowed the prices to be shown.
How's current version working (Firefox 11)? I can't reproduce it, but it may be network setup specific.
I suspect it is highly network specific. I just tried toggling the ipv6 setting and checking newegg, and it seemed to work this time even with ipv6 enabled, but I have no idea how many things might have changed since the original report.
Ahh, I see, Thanks for the info. I think there's nothing we can do with it. May it be related to your ISP?