"Recently Updated" board has stopped fitting my screen

[Brambles]

Have toggled the flag I mentioned, width is fixed but fuzzy fonts is not. If you have fuzzy fonts then try disabling 'disable directwrite windows'. Makes the fonts much sharper.

[Ripshod]

Brambles it was nothing to do with Chrome. Chrome defaults that setting to 'disabled'. Members haven't changed settings and it's fixed itself. thumb up

[Brambles]

Ah well, I am probably in another world here in my own little thoughts. You know like that guy at the end of the bar in a Pub mumbling away and no one knows what the heck he is on about -- thats me tonight happy with my Aerotank and cappuccino flavour ejuice.

[Q]

Strange that it only affected SOME people!!! I alswys have the latest version of all 3 browsers I use daily and it didn't happen to me... WEIRD

[Brambles]

Q Maybe you already have blurred wide fonts and do not realise it as so used to it -- go on post a screen shot of your screen and lets have a look.

This is what mine looks like.

[Brambles]

Interesting, just realised the font used in the quick reply box is smaller than when it is posted to the thread..then it is slightly larger. So what you see is not what you get when posted.

[Ripshod]

When you write a post in the Quick Reply box it's done in bbcode mode. When it's posted it goes to html. You can actually see this by editing one of your own posts. When you go into the editor it's in html mode, but if you click the bbcode tab at the bottom of the box it'll switch to bbcode mode, the small text again.

[Brambles]

Ripshod. Ahhhhh! never thought of that, thanks for explaining.

[Q]

Sept 10, 2014 1:26:25 GMT Brambles said:

Q Maybe you already have blurred wide fonts and do not realise it as so used to it -- go on post a screen shot of your screen and lets have a look.

This is what mine looks like.

[Brambles]

Q unfortunately you are not going to see what I see and your fonts do look blurred to me. Problem is so are images so my sharp text I captured into a picture will look blurred on your screen.

Now because I could be totally wrong, which I accept, I suggest if you have the patience is try viewing AAEC and this thread using IE or Firefox and see if the text is much sharper. If it is then Chrome is not set right, if it is just the same then may just be your display general settings and graphics driver is just not as sharp as mine, or I am talking nonsense which is quite possible.
However I also accept if it ain't broke don't fix it...that can be fatal on a computer.

Ripshod am I speaking rubbish?

[Q]

I've not had any problems Brambles and the screenshot was Firefox, I also use Chrome & Comodo Dragon and haven't had any problems with those either.
The only browser I dont use is Internet Exploder

[Ripshod]

Sept 10, 2014 14:12:36 GMT Brambles said:

Q unfortunately you are not going to see what I see and your fonts do look blurred to me. Problem is so are images so my sharp text I captured into a picture will look blurred on your screen.

Now because I could be totally wrong, which I accept, I suggest if you have the patience is try viewing AAEC and this thread using IE or Firefox and see if the text is much sharper. If it is then Chrome is not set right, if it is just the same then may just be your display general settings and graphics driver is just not as sharp as mine, or I am talking nonsense which is quite possible.
However I also accept if it ain't broke don't fix it...that can be fatal on a computer.

Ripshod am I speaking rubbish?

No, you're not speaking rubbish. The only thing I pointed out was the default for the setting you suggested is, and has always been disabled. It would only cause problems if a user had been in and changed that setting.

'If it ain't broke don't fix it' can be applied to anything really, but it definitely does apply to computers. The problem with chrome is it's so easy to change the zoom settings without realizing what you'd done or how you did it. With the zoom you can easily make any web page appear wrong, and it can be frustrating for peeps when noone else can see the problem.

Anyways, in this case it was proboard's fault. Someone probably updated a bit of code, then had to go back in and reset everything linked to it (an assumption given the evidence), they're always upgrading something.