How do they expect this forum to survive when they can't even fix basic formatting issues ?

[mike guy]

It’s not a computer setting problem. It’s the responsive grid design. This is my field and I can see the exact problem and I promise you it’s in the site side. For any site developers reading this thread. It incorrectly sizes the grid columns because it misidentifies the viewport size. I can give better details but there isn’t much point gumming up the thread with developer talk.

This is the issue, but not necessarily the fix. The fix of course has a lot more to consider, so let’s be patient with those responsible for fixing it. Manually size your browser window is a fine enough work around that makes the forum readable.

 

[normanaj]

I run linux (ubuntu mate) on my laptop and have had no issues in either the firefox or chromium browsers.None on my android phone either using firefox,chrome or opera.

Looking at the screenshots that have been posted by those being affected I can see why it would drive you insane.

 

[mike guy]

Forktender and anyone else affected by this I have another small work around.

If you are using chrome, hit f12 in your browser and select the console tab. Paste this in and hit enter:
$(".p-body-main").removeClass("p-body-main")

This somewhat fixes the issue, but you have to do it on every page turn. It's much easier to just run in a smaller browser. I'm just trying to demonstrate what the css problem with the site is.

This should also make it clear to the site developers what the problem is.
The p-body-main css class conflicts with the p-body-main--withSidebar block sizing. Probably due to using min-width instead of max-width on p-body-inner.

Hope that helps, but this is 100% a site css conflict problem and not anyone's individual settings (outside their desktop resolution and browser window size).

 

[grubby64]

forktender .
Wife recently lost half her page from her website on laptop and we kinda went through the same thing, smaller format. Other sites were fine. She accidentally hit something and it went berserk. Went to the settings(upper right corner) and Changed the zoom % and that reclaimed her screen. Dell Inspirion. Don't know if has anything to do with your issue ? ? ?

I am using Firefox browser on a Mac computer. This issue has caused me to avoid this forum lately even though I enjoy the content.
For what it's worth, I checked my zoom% as advised in the post above and because I am an old fart, I had it zoomed to 200%! I lowered it to 150% and boom! Problem fixed!
I hope this helps others to find a solution.

 

[tallbm]

Forktender and anyone else affected by this I have another small work around.

If you are using chrome, hit f12 in your browser and select the console tab. Paste this in and hit enter:
$(".p-body-main").removeClass("p-body-main")

This somewhat fixes the issue, but you have to do it on every page turn. It's much easier to just run in a smaller browser. I'm just trying to demonstrate what the css problem with the site is.

This should also make it clear to the site developers what the problem is.
The p-body-main css class conflicts with the p-body-main--withSidebar block sizing. Probably due to using min-width instead of max-width on p-body-inner.

Hope that helps, but this is 100% a site css conflict problem and not anyone's individual settings (outside their desktop resolution and browser window size).

Nice find!

With that info a site admin could go and update the CSS and have this fixed pretty quickly.

I'm giggling a bit at how you went and debugged this on your own hahahahaha but thanks for taking the time. Now its just a matter of getting the changes applied and confirming it works well.
As you know with this line of work you fix or change 1 thing to find 5 more in waiting :D

Great info!!! :)

 

[hellasteph]

Hi all! Thanks for reporting this. It seems like there is a misunderstanding that we didn't or won't fix this. The initial investigation didn't let us reproduce this problem until others mentioned that it's in a "no ads" view. It was very specific to a limited group so our team could not reproduce it readily.

After everyone's great input and feedback, we were able to get the exact issue reproduced through trial and error. We kindly ask that if and when you report these issues, that additional information be included to help us get this resolved sooner than later by:

1. Including the computer and browser systems you're using (i.e. PC and Chrome browser or iPhone and Safari mobile)
2. Include a screenshot, a URL to the exact page(s) you're seeing this problem on, and what area you're looking at. The entire site is very vast and big, so we want to continue to test to see if we fixed the problem after we push a fix live.
3. Finally, disable all your extensions / plugins / add-ons, and see if the problem persists. If the issue persists, let us know.

Thank you for your patience and help in resolving this!

 

[Winterrider]

Forktender and anyone else affected by this I have another small work around.

If you are using chrome, hit f12 in your browser and select the console tab. Paste this in and hit enter:
$(".p-body-main").removeClass("p-body-main")

This somewhat fixes the issue, but you have to do it on every page turn. It's much easier to just run in a smaller browser. I'm just trying to demonstrate what the css problem with the site is.

This should also make it clear to the site developers what the problem is.
The p-body-main css class conflicts with the p-body-main--withSidebar block sizing. Probably due to using min-width instead of max-width on p-body-inner.

Hope that helps, but this is 100% a site css conflict problem and not anyone's individual settings (outside their desktop resolution and browser window size).

Huh. . . ? ? ?
That would be completely over my head.
Excellent on your part to find that. I don't have a clue on what f-1thru12 even do. I just don't touch.

 

[indaswamp]

I may have lost track. But what other members have the same problem?

Me...
I have the same issue Steve.

 

[chopsaw]

Should be fixed now .

 

[indaswamp]

Thank you for posting Mike Guy. Hope this helps the techs. resolve the issue.