"Recently Updated" board has stopped fitting my screen

[Ripshod]

There are no errors showing anywhere. Page sizes have not change since Sunday.

I've got to ask. Has anyone with these problems changed any settings recently to make a webpage more readable?

I got to admit tho, the whole site looks like it's been made wider. This could be down to the staff or proboards, only Chrissie can answer that one.

[Greg]

Same issue on ipad

[Brambles]

Ripshod and others with issues


In Chrome://flags (type this in Chrome address bar) change the setting for 'disable Directdraw windows' ( 3rd setting down I think). The flag setting should be showing 'disable' and then relaunch Chrome using button at bottom of page.

For bit more details see here productforums.google.com/forum/#!category-topic/chrome/YorPy_uctMI .
Basically the latest version of chrome is creating a problem with fuzzy and wider fonts, and naturally you do any of these changes at your own risk and you should only attempt this if you are computer savvy.

[Ripshod]

I've never had this issue. I still don't get the issue with the latest version of Chrome I've just installed. DirectDraw is disabled by default. It happens in other browsers. Not a Chrome problem.

Upgraded FF, still don't get this issue.

[Chrissie]

Sept 9, 2014 16:43:53 GMT Ripshod said:

There are no errors showing anywhere. Page sizes have not change since Sunday.

I've got to ask. Has anyone with these problems changed any settings recently to make a webpage more readable?

I got to admit tho, the whole site looks like it's been made wider. This could be down to the staff or proboards, only Chrissie can answer that one.

I've not changed the width of the forum or any other settings.

[Greg]

Sept 9, 2014 16:48:51 GMT Greg said:

Same issue on ipad

All good now but I didn't change anything.

[ionian]

Sept 9, 2014 19:47:38 GMT Greg said:

Sept 9, 2014 16:48:51 GMT Greg said:

Same issue on ipad

All good now but I didn't change anything.

Same here - all fine now with no changes to my settings. 

[Chrissie]

Sept 9, 2014 19:47:38 GMT Greg said:

Sept 9, 2014 16:48:51 GMT Greg said:

Same issue on ipad

All good now but I didn't change anything.

Neither did I Greg So it sounds like it is a browser issue that is being resolved?

[Ripshod]

Sept 9, 2014 19:44:14 GMT Chrissie said:

I've not changed the width of the forum or any other settings.

Thanks Chrissie. So as it's not browser related we can only assume it's a proboards issue.

And as Greg has posted that it's resolved then it looks fixed. Just need OneDay to confirm.

[Mev]

don't panic !!! got the magic wand out..

[Pepperty]

I'm wondering if proboards set forums by pixels, rather than by percent? and have been made aware so altered, can only assume that ??? Percent figures are always safer as theres no telling what screen resolution people use..

[Ripshod]

I tested that Pepperty. The pixel count does change as you reduce the window. I always used to use percents when building pages, but obviiously you can only let it get so low before you have to lock it. Hence a lot of sites state that they are best viewed at ****x*** resolution. The minimum I'd set was 1024px wide, for those with older monitors. But there's so many smaller smart devices these days you can't please evryone.

[Chrissie]

Sept 9, 2014 20:01:57 GMT Pepperty said:

I'm wondering if proboards set forums by pixels, rather than by percent? and have been made aware so altered, can only assume that ??? Percent figures are always safer as theres no telling what screen resolution people use..

Pepperty, as admin, I have a choice as to whether to set the forum width as a percentage or pixels - I've always had it set as a percentage.

[OneDay]

Sept 9, 2014 19:53:00 GMT Ripshod said:

Sept 9, 2014 19:44:14 GMT Chrissie said:

I've not changed the width of the forum or any other settings.

Thanks Chrissie. So as it's not browser related we can only assume it's a proboards issue.

And as Greg has posted that it's resolved then it looks fixed. Just need OneDay to confirm.

Normality has been restored here too, without altering any settings

[Brambles]

It was a bug in last update of Chrome, they may have probably fixed it.