hawker wrote:
On 11/29/2011 9:23 AM, WLS wrote:
On 11/29/2011 09:13 AM, hawker wrote:
Reading along there appears to be a change in the SM 2.5
rendering engine that makes a small number of sites unreadable. I
trying to grasp how big this issue is (IE how likely am I to run
across this), and is there some known small issue causing this
with a 2.5.1 patch coming up?
I have already found a decent number of sites that work fine in
FireFox 3.x or IE8 but not Seamonkey 2.x and I deal with it by
occasionally using, gasp, IE but this sounds like it might be
bigger than that so I'm wondering if I should hold off a few
weeks again?
Links to those site could be helpful. I've never had a problem
with SeaMonkey 2.x versions.
I'd be happy to test them in SeaMonkey 2.6b1.
As to the Seamonkey 2.5 issues, I got this from reading here and
folks listing a few sites here and there, especially it seems, some
routers.
Most of the complaints about a site not working in SeaMonkey are due to
author cluelessness, by sniffing for browser names that don't include
SeaMonkey (i.e. they test for IE, Firefox, Safari in the UA string and
none of the lesser-known browsers).
So I have not tested these in recent FF versions. But a while ago
these two sites worked fine in FF and IE8 but not IE7 or Seamonkey.
http://www.taurusbass.com/ Note the two buttons on top of each other
(in/register and visitors) It looks fine in FF and IE
Your taurusbass site works fine for me in Firefox 8.0, SeaMonkey 2.4.1,
Opera 11.52. Those "buttons" are no more than textual links with CSS
styling, not real buttons.
That's for the public portions of the site; I have no login. I don't use
Windows, so no IE here. I did not see any browser sniffing in the code.
Try it with all your add-ons disabled.
--
-bts
-This space for rent, but the price is high
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
