Poor Rendering...

User Help for Seamonkey and Mozilla Suite
Post Reply
Johnfull
Posts: 1463
Joined: November 10th, 2004, 5:18 am

Poor Rendering...

Post by Johnfull »

This webpage used to display properly, but is now not fitting the frame.
The righthand end and the bottom of the image are cropped, including the controls.

http://www.cbsnews.com/live/

Any idea why it changed and what to restore it?...
User avatar
DanRaisch
Moderator
Posts: 127243
Joined: September 23rd, 2004, 8:57 pm
Location: Somewhere on the right coast

Re: Poor Rendering...

Post by DanRaisch »

Does the same thing occur if you launch the application in Mozilla Safe Mode? http://kb.mozillazine.org/Safe_mode
TPR75
Posts: 1353
Joined: July 25th, 2011, 8:11 am
Location: Poland

Re: Poor Rendering...

Post by TPR75 »

Johnfull wrote:This webpage used to display properly, but is now not fitting the frame.
The righthand end and the bottom of the image are cropped, including the controls.

http://www.cbsnews.com/live/

Any idea why it changed and what to restore it?...
Works OK for me.

There is Flash Player. Try to disable "Hardware acceleration" within Flash: click RMB somewhere on Flash Player -> Settings -> Display -> uncheck "hardware acceleration".

Disable P2P function for Flash: click RMB somewhere on Flash Player -> Global Settings -> middle tab (something with "playing") -> block P2P (what its name there).

Did it helped a little?
--
User avatar
WaltS48
Posts: 5141
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Re: Poor Rendering...

Post by WaltS48 »

It worked OK for TPR75 because they have "Advertise Firefox compatibility" disabled in Preferences > Advanced > HTTP Networking as I just confirmed in my own SeaMonkey. Notice the UA string in their post.

Fits the frame when the pref is disabled, doesn't fit the frame when the pref is enabled.
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: Poor Rendering...

Post by rsx11m »

It's interesting to see that the compatibility token actually hurts in some cases while is was introduced explicitly to help other Gecko applications to "look" like Firefox to websites... :-k
User avatar
WaltS48
Posts: 5141
Joined: May 7th, 2010, 9:38 am
Location: Pennsylvania, USA

Re: Poor Rendering...

Post by WaltS48 »

rsx11m wrote:It's interesting to see that the compatibility token actually hurts in some cases while is was introduced explicitly to help other Gecko applications to "look" like Firefox to websites... :-k
Probably fixed when 2.46 ships. :?:
Linux Desktop - AMD Athlon(tm) II X3 455 3.3GHz | 8.0GB RAM | GeForce GT 630
Windows Notebook - AMD A8 7410 2.2GHz | 6.0GB RAM | AMD Radeon R5
Anonymosity
Posts: 8779
Joined: May 7th, 2007, 12:07 pm

Re: Poor Rendering...

Post by Anonymosity »

WaltS48 wrote:
rsx11m wrote:It's interesting to see that the compatibility token actually hurts in some cases while is was introduced explicitly to help other Gecko applications to "look" like Firefox to websites... :-k
Probably fixed when 2.46 ships. :?:
No, not fixed. I am using a Tinderbox build of 2.46, and that page is still messed up.
rsx11m
Moderator
Posts: 14404
Joined: May 3rd, 2007, 7:40 am
Location: US

Re: Poor Rendering...

Post by rsx11m »

Nothing to fix here on SeaMonkey's side: It'll either send that token or it won't, depending on that checkbox.
You have to complain to the website maintainers to fix their browser sniffing.

See http://forums.mozillazine.org/viewtopic ... &t=3024661 for another example (in that case based on the Lightning token).
Post Reply