Yesterday we were trying to figure out why no prices show up on newegg.com on a friend's rhel 6 system when visiting it with firefox. The only google results I found was someone with the same problem when he disabled javascript (but javascript was not disabled).
Today I tried it on my fedora 16 boot partition with firefox 7.0.1, and by golly, I see the same problem. The box in the middle of the page that normally has the price info and the add to cart button is not showing the price (or the button).
Is javascript busted in f16? Does anyone else have a problem with newegg showing prices? The specific web page I visited was:
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
Anyone else see the same problem with newegg?
On Thu, Nov 03, 2011 at 08:03:25AM -0400, Tom Horsley wrote:
Yesterday we were trying to figure out why no prices show up on newegg.com on a friend's rhel 6 system when visiting it with firefox. The only google results I found was someone with the same problem when he disabled javascript (but javascript was not disabled).
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
By golly, you're right. I normally use chrome or opera, so didn't see it, but I see, opening that link with Firefox on F16, that I have the same issue. Opening it with chrome is fine.
On Thu, 3 Nov 2011 08:12:43 -0400 Scott Robbins wrote:
On Thu, Nov 03, 2011 at 08:03:25AM -0400, Tom Horsley wrote:
Yesterday we were trying to figure out why no prices show up on newegg.com on a friend's rhel 6 system when visiting it with firefox. The only google results I found was someone with the same problem when he disabled javascript (but javascript was not disabled).
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
By golly, you're right. I normally use chrome or opera, so didn't see it, but I see, opening that link with Firefox on F16, that I have the same issue. Opening it with chrome is fine.
To add even more confusion, if I (Gasp!) run firefox as root on fedora 16, I can see the newegg prices, it is only when run as a plain old user that I can't see the prices (and I have tried safe mode and making a brand new .mozilla directory, etc - none of that stuff works). Is some piece of javascript installed with permissions that only allow root to run it? This is really weird.
On Thu, Nov 03, 2011 at 08:35:33AM -0400, Tom Horsley wrote:
On Thu, 3 Nov 2011 08:12:43 -0400 Scott Robbins wrote:
On Thu, Nov 03, 2011 at 08:03:25AM -0400, Tom Horsley wrote:
By golly, you're right. I normally use chrome or opera, so didn't see it, but I see, opening that link with Firefox on F16, that I have the same issue. Opening it with chrome is fine.
To add even more confusion, if I (Gasp!) run firefox as root on fedora 16, I can see the newegg prices, it is only when run as a plain old user that I can't see the prices (and I have tried safe mode and making a brand new .mozilla directory, etc - none of that stuff works). Is some piece of javascript installed with permissions that only allow root to run it? This is really weird.
Nope, if I run it as root (in fluxbox--as normal user I'm using openbox), I still don't get the prices.
On Thu, 2011-11-03 at 08:12 -0400, Scott Robbins wrote:
On Thu, Nov 03, 2011 at 08:03:25AM -0400, Tom Horsley wrote:
Yesterday we were trying to figure out why no prices show up on newegg.com on a friend's rhel 6 system when visiting it with firefox. The only google results I found was someone with the same problem when he disabled javascript (but javascript was not disabled).
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
By golly, you're right. I normally use chrome or opera, so didn't see it, but I see, opening that link with Firefox on F16, that I have the same issue. Opening it with chrome is fine.
It works here, and I'm even using noscript (though I've allowed newegg)...
On Thu, 03 Nov 2011 05:44:44 -0700 Adam Williamson wrote:
It works here, and I'm even using noscript (though I've allowed newegg)...
Weird. If only we could figure out what is different :-).
In any case, since I got confirmation that at least one other person sees the bug, I added a bugzilla for it:
On Thursday 03 Nov 2011 08:03:25 Tom Horsley wrote:
Yesterday we were trying to figure out why no prices show up on newegg.com on a friend's rhel 6 system when visiting it with firefox. The only google results I found was someone with the same problem when he disabled javascript (but javascript was not disabled).
Today I tried it on my fedora 16 boot partition with firefox 7.0.1, and by golly, I see the same problem. The box in the middle of the page that normally has the price info and the add to cart button is not showing the price (or the button).
Is javascript busted in f16? Does anyone else have a problem with newegg showing prices? The specific web page I visited was:
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
Anyone else see the same problem with newegg?
Its working fine here, firefox 7.0.1 f16
Martin
On Thu, Nov 03, 2011 at 08:16:52AM -0500, Michael Cronenworth wrote:
On 11/03/2011 07:03 AM, Tom Horsley wrote:
Anyone else see the same problem with newegg?
I would have to guess it is a video driver issue instead of a Firefox issue. You might want to state the video card and driver you are using (proprietary or otherwise).
Interesting. In my case
nVidia Corporation C61 GeForce 6150SE (from lspci)
Using the default nouveau driver.
On 11/03/2011 08:25 AM, Scott Robbins wrote:
On Thu, Nov 03, 2011 at 08:16:52AM -0500, Michael Cronenworth wrote:
On 11/03/2011 07:03 AM, Tom Horsley wrote:
Anyone else see the same problem with newegg?
I would have to guess it is a video driver issue instead of a Firefox issue. You might want to state the video card and driver you are using (proprietary or otherwise).
Interesting. In my case
nVidia Corporation C61 GeForce 6150SE (from lspci)
Using the default nouveau driver.
Have you turned all of your addons off in FireFox and then gone to NewEgg? I see this type of issue sometimes on other websites until I play around with my noscripts addon and "allow" things.
Kevin
On Thu, Nov 03, 2011 at 08:53:15AM -0500, Kevin Martin wrote:
On 11/03/2011 08:25 AM, Scott Robbins wrote:
On Thu, Nov 03, 2011 at 08:16:52AM -0500, Michael Cronenworth wrote:
On 11/03/2011 07:03 AM, Tom Horsley wrote:
Anyone else see the same problem with newegg?
I would have to guess it is a video driver issue instead of a Firefox issue. You might want to state the video card and driver you are using
nVidia Corporation C61 GeForce 6150SE (from lspci)
Using the default nouveau driver.
Have you turned all of your addons off in FireFox and then gone to NewEgg? I see this type of issue sometimes on other websites until I play around with my noscripts addon and "allow" things.
Ahah, I see I had adblock. I've disabled it and restarted firefox but still no joy.
On 2011/11/03 08:16 (GMT-0500) Michael Cronenworth composed:
On 11/03/2011 07:03 AM, Tom Horsley wrote:
http://www.newegg.com/Product/Product.aspx?Item=N82E16819115070 Anyone else see the same problem with newegg?
I would have to guess it is a video driver issue instead of a Firefox issue. You might want to state the video card and driver you are using (proprietary or otherwise).
I'd be shocked if you turned out to be right about a video driver being at fault.
More likely candidates: 1-IPV6 vs IPV4 2-extensions 3-site scripting: Newegg adjusts various sizes of objects according to what it discovers about your browser settings, like viewport size, screen resolution and default font size
On Thu, 03 Nov 2011 13:25:21 -0400 Felix Miata wrote:
1-IPV6 vs IPV4
Bingo! You are a genius! I had ipv6 disabled in my fedora 15 about:config in firefox, on fedora 16 I had the default enabled setting. When I disable it on f16, I can see the prices again.
Apparently it can't lookup the IP for content.newegg.com when ipv6 is enabled (though it can lookup everything else with no obvious problem :-).
On 11/03/2011 03:09 PM, Tom Horsley wrote:
Bingo! You are a genius! I had ipv6 disabled in my fedora 15 about:config in firefox, on fedora 16 I had the default enabled setting. When I disable it on f16, I can see the prices again.
Apparently it can't lookup the IP for content.newegg.com when ipv6 is enabled (though it can lookup everything else with no obvious problem:-).
Sorry, but IPv6 has nothing to do with your problem and changing the preference is just coincidental.
On 11/03/2011 03:16 PM, Michael Cronenworth wrote:
On 11/03/2011 03:09 PM, Tom Horsley wrote:
Bingo! You are a genius! I had ipv6 disabled in my fedora 15 about:config in firefox, on fedora 16 I had the default enabled setting. When I disable it on f16, I can see the prices again.
Apparently it can't lookup the IP for content.newegg.com when ipv6 is enabled (though it can lookup everything else with no obvious problem:-).
Sorry, but IPv6 has nothing to do with your problem and changing the preference is just coincidental.
Hmm, don't know that I agree with that. I've seen issues in other places with IPV6 turned on or off respectively. Perhaps the correct way to test that is to make sure to run firefox with all extensions turned off, IPV6 set on, see what newegg.com looks like, turn off IPV6, checkout newegg.com again. That way you are sure that extensions are doing something weird and can verify the validity of IPV6 getting in the way or not.
Kevin
On 11/03/2011 03:30 PM, Kevin Martin wrote:
Hmm, don't know that I agree with that. I've seen issues in other places with IPV6 turned on or off respectively. Perhaps the correct way to test that is to make sure to run firefox with all extensions turned off, IPV6 set on, see what newegg.com looks like, turn off IPV6, checkout newegg.com again. That way you are sure that extensions are doing something weird and can verify the validity of IPV6 getting in the way or not.
The price is ASCII text embedded in the HTML page. IPv6 has absolutely nothing to do with this issue. You could view the source code of the page and find the price. It is a rendering problem (that I, and others cannot reproduce).
There is no mythical IPv6 monster eating your bytes. I hate that this "disabling IPv6 fixed it" myth exists. Pretty soon you will have to enable IPv6 to even get on the Internet.
On 11/03/2011 04:35 PM, Michael Cronenworth wrote:
The price is ASCII text embedded in the HTML page.
Actually, if I understood correctly, what I believe he said was that the price data was fetched and inserted into the page by JavaScript, and the JavaScript code in question was unable to resolve the host name it needed to contact to fetch the price.
There is no mythical IPv6 monster eating your bytes. I hate that this "disabling IPv6 fixed it" myth exists.
If the host has an IPv6 address, and if either (a) the IPv6 address isn't reachable or (b) there's something messed up in the IPv6 configuration on your end, such that /no/ IPv6 address is reachable, then it's entirely plausible that disabling IPv6 could fix an issue like this.
jik
On 11/03/2011 03:45 PM, Jonathan Kamens wrote:
Actually, if I understood correctly, what I believe he said was that the price data was fetched and inserted into the page by JavaScript, and the JavaScript code in question was unable to resolve the host name it needed to contact to fetch the price.
Yes, it is fetched with JavaScript. See below.
If the host has an IPv6 address, and if either (a) the IPv6 address isn't reachable or (b) there's something messed up in the IPv6 configuration on your end, such that /no/ IPv6 address is reachable, then it's entirely plausible that disabling IPv6 could fix an issue like this.
Newegg doesn't have a single IPv6 address attached to any of their domains. That's also ignoring the fact that Firefox, as well as glibc, will start with a IPv4 address by default unless it detects you have a real (non 6to4) IPv6 default route. Toggling a little setting in Firefox will do jack squat.
Explain yourself out of that one. I'm done with this thread.
On Thu, 03 Nov 2011 15:50:40 -0500 Michael Cronenworth wrote:
Toggling a little setting in Firefox will do jack squat.
If by "jack squat" you mean make it work versus not work, you are right.
Explain yourself out of that one.
Explain why "jack squat" equates to 100% correlation with working versus not working with as many tests as you care to make.
On 11/03/2011 04:50 PM, Michael Cronenworth wrote:
Explain yourself out of that one. I'm done with this thread.
I do not understand why you feel the need to be so confrontational and hostile about this issue. It is neither productive nor helpful, and it has the tendency to scare off testers from providing useful feedback.
Neither the OP nor I can explain /why/ his system behaves the way it does. But his system is clearly behaving that way, and being able to explain why is not a prerequisite to being able to share whatever information we do know in the hope that it will be helpful to others.
jik
//
On Thu, 03 Nov 2011 15:35:48 -0500 Michael Cronenworth wrote:
The price is ASCII text embedded in the HTML page. IPv6 has absolutely nothing to do with this issue. You could view the source code of the page and find the price. It is a rendering problem (that I, and others cannot reproduce).
No, the price is ascii text embedded in the javascript obtained from content.newegg.com, and with ip6v enabled firefox and wget consistently fail to resolve the IP for content.newegg.com.
There is no mythical IPv6 monster eating your bytes.
True: There is an *actual* IPv6 monster eating the DNS for content.newegg.com, no myth. 100% correlation with turning the flag on and off in firefox as many times as I care to test it.
Almost certainly nothing to do with firefox itself though, more likely some combination of strange an wondrous problems with firewalls and DNS server forwarding and wot-not on the long an winding road out of the corporate firewall I was inside to the actual lookup of content.newegg.com (but there are a gazillion other <whatever>.newegg.com URLs it has no problem resolving).
On Thu, Nov 03, 2011 at 04:09:57PM -0400, Tom Horsley wrote:
On Thu, 03 Nov 2011 13:25:21 -0400 Felix Miata wrote:
1-IPV6 vs IPV4
Bingo! You are a genius! I had ipv6 disabled in my fedora 15 about:config in firefox, on fedora 16 I had the default enabled setting. When I disable it on f16, I can see the prices again.
Yup, that fixed it for me too.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/11 13:03, Tom Horsley wrote:
On my fedora 15 system with firefox 7.0.1, the price does appear. Same version of firefox, so I really don't understand what is happening here :-).
Anyone else see the same problem with newegg?
I can't reproduce this.
firefox-7.0.1-3.fc16.x86_64
Further more: is this a bug in fedora or is this a bug on this special web page? I would say the latter, although I understand your annoyance.
Matthias - -- Matthias Runge mrunge@matthias-runge.de mrunge@fedoraproject.org