flyguy wrote:
[email protected] wrote on 2/12/2017 12:13 PM:
flyguy wrote:
Perhaps this related to a Google problem that began in the last
couple of months. For example, if I type in "pizza" (no quote
marks), I get the usual ad links, a small map showing pizza
places in the area, under which is a list of those places.
Clicking on a pizza place in the list takes me to another tab,
which remains blank with status line showing "done". I used get
what I still get in IE and Chrome: the list of places, and a full
map overlaid with box showing the details of the place I clicked
on.

I can get the usual full map, etc, if I click on the "Maps" link
the menu that's under the Google search box at the top.

After a bit more experimenting, it seems that it may be necessary to
check a few other settings as well:
- Enable JavaScript for Google (in case you've disabled it, or
using a script blocker like NoScript)
- Set the user-agent for www.google.co.uk (or your local variant)
to a Firefox user-agent
- Turn OFF "Advertise Firefox compatibility"

BINGO! I've always had Javascript enabled, so I just disabled
"Advertise Firefox compatibility" and worked just like it used for
several years. Remarkable sleuthing - thanks very much. These were
really frustrating problems, especially as IE and Chrome didn't seem
to have problems.

Anyway, do you think Google and the New York times have changed how
they do things in the last month or so? Or does Seamonkey have glitch
in it?

I've no idea; the behaviour of web sites can change at any time, some more frequently than others. If the change coincided with upgrading SeaMonkey, it's probably a change in SeaMonkey's behaviour. Not necessarily a glitch in SeaMonkey even then though - it might even be that something that was wrong but happened to make those sites work has been fixed.

The way those sites are trying to detect the browser and serve different content is fundamentally broken. Browsers try to get around the problem by including all sorts of things they're not in the user-agent sting (e.g. IE and Chrome include "Mozilla/5.0" and "like Gecko", and SeaMonkey has an "Advertise Firefox compatibility" option to add a Firefox version into the string) but whether it works depends on exactly what a particular site is looking for in the string.

In theory, pages should render the same with SeaMonkey as they do with Firefox. But when a web site explicitly detects Firefox (and other browsers) and sends different content, SeaMonkey doesn't get the same page as Firefox and the result depends on whatever the server does send to SeaMonkey. Most sites doing that kind of thing make sure they work with major browsers (IE, Firefox, Chrome, maybe one or two others) and don't even consider others like SeaMonkey. If they work with SeaMonkey it's more by luck than design, and informing them of a problem is usually met with a response telling you to use one of the browsers they design for (which is far easier for them than actually fixing their design to just work regardless of the browser).

--
Mark.

_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to