Re: [Solved] Re: [Linux] Google Maps Directions - Printing Large Map
On 12/28/10 9:15 PM, Ant wrote: On 12/27/2010 10:54 PM PT, NoOp typed: ... 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). Wait, v2.1 beta is using Firefox in its user agent? Um, why? That's not a true user agent for SeaMonkey. :( I agree. However, it seems this is a done deal. It was discussed thoroughly both here and in the bug report. See https://bugzilla.mozilla.org/show_bug.cgi?id=572650. Apparently, Robert Kaiser was not happy about this. See https://bugzilla.mozilla.org/show_bug.cgi?id=591617. The result of all this has been several bug reports against Mozilla Web sites -- especially https://addons.mozilla.org/ -- that sniff the UA string. It appears that all aspects of this change were not really evaluated. Bug #572650 may be breaking more than it fixes. Note that, this bug report really does not describe a discrepancy in software; yet the developers refuse to classify it as an RFE (request for enhancement). -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [Solved] Re: [Linux] Google Maps Directions - Printing Large Map
David E. Ross wrote: On 12/28/10 9:15 PM, Ant wrote: On 12/27/2010 10:54 PM PT, NoOp typed: ... 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). Wait, v2.1 beta is using Firefox in its user agent? Um, why? That's not a true user agent for SeaMonkey. :( I agree. However, it seems this is a done deal. It was discussed thoroughly both here and in the bug report. See https://bugzilla.mozilla.org/show_bug.cgi?id=572650. Apparently, Robert Kaiser was not happy about this. See https://bugzilla.mozilla.org/show_bug.cgi?id=591617. The result of all this has been several bug reports against Mozilla Web sites -- especiallyhttps://addons.mozilla.org/ -- that sniff the UA string. It appears that all aspects of this change were not really evaluated. Bug #572650 may be breaking more than it fixes. Note that, this bug report really does not describe a discrepancy in software; yet the developers refuse to classify it as an RFE (request for enhancement). When you first install the SM-2.1 (currently b2pre), the Firefox UA probably is turned-on by-default, but it is easily toggled-off via the menu:- Edit Preferences Advanced HTTP-networking User Agent String and uncheck the Advertise Firefox compatibility box. No about:config scenario required. I can't remember what the initial state is as I usually have it off, but it probably is turned-on to allow new users and people like me who forget to turn it back on when encountering problem sites, to surf without having to deal with that extra angst. Oh, through dozens/hundreds of nightly upgrades which completely-clear the entire application-folder, but not the profile, the Firefox-UA-switch stays turned-off, in accordance with my preferences. HTH. Barry. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: [Solved] Re: [Linux] Google Maps Directions - Printing Large Map
On 12/27/2010 10:54 PM PT, NoOp typed: ... 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). Wait, v2.1 beta is using Firefox in its user agent? Um, why? That's not a true user agent for SeaMonkey. :( -- Ah. Those club kids did eat those ants up like popcorn. --CSI: Miami (Wannabe episode; #218) /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
[Solved] Re: [Linux] Google Maps Directions - Printing Large Map
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 support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
