On 12/27/2010 05:07 PM, David E. Ross wrote:
...
> 
> This seems to be another case of screwed-up sniffing.
> 
> All of the following were done with SeaMonkey 2.0.11.
> 
> With the UA string
>    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16)
>       Gecko/20101123 SeaMonkey/2.0.11
> both the map and the blue overlaid route appear okay in my browser
> window.  The the overlaid route DOES NOT appear in any print operation,
> including preview.  Thus, the problem is not related to whether the
> operating system is Windows or Linux.
> 
> With the UA string
>    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13)
>       Gecko/20101203 Firefox/3.6.13
> both the map and the blue overlaid route appear okay in my browser
> window.  The the overlaid route DOES indeed appear in print operations,
> including preview.
> 
> In the case of SM 2.1b2pre, I suspect the "pre" is the key :-)  Google
> Maps might have sniffed this as being for a Pre smart phone, in which
> case the mapping apparently works.  (Not having -- or wanting -- any
> smart phone, I can't test that.)  However, the experience of Barry
> Gilmour indicates otherwise.  Maybe it's the combination of "pre" and
> "KDE" that works.  Also not having Linux, this is another one I can't
> test.

You are correct, it is a case of browser sniffing. Just changed to:
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3)
Gecko/20090824 Firefox/3.5.3
and print preview & printing now includes the overlay. Also figured out
why it was working in my WinXP virtual machine. I have two versions of
SeaMonkey installed: 2.0.11 and 2.1b2pre. I had clicked hte 2.1b2pre
version for the test & thought that I had clicked the 2.0.11. The reason
why the 2.1b version works is that the UA string includes "Firefox" in
the UA string (as Barry also pointed out).

> 
> In the case of Opera, it might be a browser that Google ignores while
> sniffing.
> 
> I found four open bug reports about invalid sniffing by Google.  While
> two of them address problems with Google Maps, none of them specifically
> address this problem.  I have submitted bug report #621619; see
> <https://bugzilla.mozilla.org/show_bug.cgi?id=621619>.

Thanks.

> 
> The problem will not be fixed unless the Web site owner is informed.
> (It might still not be fixed.)  NoOp is now responsible for notifying
> Google of the problem; I won't.  You might want to read my
> <http://www.rossde.com/internet/sniffing.html> before notifying Google.

Now I just have to figure out how to file a bug report with Google...
Only way I've found is to use the "Report a problem" on the Maps page.
I'll try that, but suspect it will go into the Google ether.



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

Reply via email to