Re: SeaMonkey Faulty Page Rendering

[Ed Mullen]

Daniel wrote:

James Greenidge wrote:

Such a situation -- works with Firefox but not with SeaMonkey --
generally indicates that the Web server is doing invalid sniffing. For
an explanation of sniffing and how to defeat it, see my
.
-- David E. Ross

I much appreciate your response, but the only thing is I'm not really a
techie and can't make heads or tails how to tinker with computer
programs, so is there any "turn key" fix to this or do you think it'll
be corrected in the next SeaMonkey issue?

Thanks!

Jim



I believe SeaMonkey 2.1 will include the word "Firefox" in its
identification string to get around web sites incorrect sniffing.


It already does in the pre-releases as the standard UA ID.

Build identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b7pre) 
Gecko/20101008 Firefox/4.0b7pre SeaMonkey/2.1b1


--
Ed Mullen
http://edmullen.net/
Attempt to get a new car for your spouse-it'll be a great trade!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Faulty Page Rendering

[Daniel]

James Greenidge wrote:

Such a situation -- works with Firefox but not with SeaMonkey --
generally indicates that the Web server is doing invalid sniffing. For
an explanation of sniffing and how to defeat it, see my
.
-- David E. Ross

I much appreciate your response, but the only thing is I'm not really a
techie and can't make heads or tails how to tinker with computer
programs, so is there any "turn key" fix to this or do you think it'll
be corrected in the next SeaMonkey issue?

Thanks!

Jim



I believe SeaMonkey 2.1 will include the word "Firefox" in its 
identification string to get around web sites incorrect sniffing.


SM 2.1 is supposed to be coming out early 2011.

Daniel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Faulty Page Rendering

[James Greenidge]

Such a situation -- works with Firefox but not with SeaMonkey -- 
generally indicates that the Web server is doing invalid sniffing. For 
an explanation of sniffing and how to defeat it, see my 
.

-- David E. Ross

I much appreciate your response, but the only thing is I'm not really a 
techie and can't make heads or tails how to tinker with computer 
programs, so is there any "turn key" fix to this or do you think it'll 
be corrected in the next SeaMonkey issue?


Thanks!

Jim

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Faulty Page Rendering

[JeffM]

David E. Ross wrote:
>Such a situation -- works with Firefox but not with SeaMonkey --
>generally indicates that the Web server is doing invalid sniffing.
>
...and the decision tree
for any browser *other* than the **one** horribly broken browser
doesn't need to be as complex as they are making it.

---Internet Exploder?---No---Deliver a proper HTML page
|
   Yes
|
 ---IE5.5?---Deliver a page coded especially for IE5.5
|
 ---IE6?---Deliver a page coded especially for IE6
|
 ---IE7?---Deliver a page coded especially for IE7
|
 ---IE8?---Deliver a page coded especially for IE8
|
 ---IE9?---Deliver a page coded especially for IE9

(It's only M$'s crap that makes sniffing necessary at all.)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Faulty Page Rendering

[David E. Ross]

On 11/19/10 4:45 AM, James Greenidge wrote:
> 
> I've come across several examples of this while using Google translation 
> service, where SeaMonkey doesn't render right while Firefox does 
> perfectly, as an example: http://sorairofact.blog.shinobi.jp/
> 
> via Google translation the page results between SeaMonkey and Firefox 
> are strikingly different in missed data and rendering:
> 
> http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fsorairofact.blog.shinobi.jp%2F&sl=ja&tl=en&history_state0=
> 
> JimWG

Such a situation -- works with Firefox but not with SeaMonkey --
generally indicates that the Web server is doing invalid sniffing.  For
an explanation of sniffing and how to defeat it, see my
.

-- 

David E. Ross


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

SeaMonkey Faulty Page Rendering

[James Greenidge]

I've come across several examples of this while using Google translation 
service, where SeaMonkey doesn't render right while Firefox does 
perfectly, as an example: http://sorairofact.blog.shinobi.jp/


via Google translation the page results between SeaMonkey and Firefox 
are strikingly different in missed data and rendering:


http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fsorairofact.blog.shinobi.jp%2F&sl=ja&tl=en&history_state0=

JimWG




___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey