[assassin10000]

It's been a few days and there is a minor sizing issue of some kind. I it noticed immediately but figured it may be one of those things still being fixed. In any case on my android phone and chrome browser I see that sub-forum listings are slightly clipped as well as the quick reply box at the bottom of a page.







Some older threads are cut off and not fully readable in either portrait or landscape orientation.

 

[HipHopScribe]

I'm having the same issue on Android using Chrome

 

[AxelCloris]

Thank you for the report. We'll have our team take a look at this.

 

[elira]

using iPhone X latest iOS and Safari, the layout of the page moves to the left and removes the first letters of every line.

 

[Currawong]

I have a slight left-shift on desktop Safari as well, which stays even after posting.

 

[Slater]

Agreed. I too am seeing the exact same ‘left cutoff’ problem on iPhone.

Even with this exact post. I have to basically guess what I typed to the left, and hope that I spelled everything ok.

I attached a photo of this post to show.

 

[AxelCloris]

Thank you for the reports, everyone. Our team is currently looking into this one.

 

[assassin10000]

So a few more small problems I've noticed:

1. Certain posts with links do not 'word wrap' correctly and are not visible or scrollable.
2. Signatures do not display.
3. Number of posts & likes no longer display next to avatar & below usernames.

Android phone on 10/Q, latest update chrome browser.

 

[NA Blur]

Noticed this too. +1

 

[Tooros]

Same.

 

[tcellguy]

I'm also having problems on the desktop Safari browser. I can only see a single page of posts and often can't see posts above mine. Also the page counter is gone so I can't move forward or back in a thread. Finally, like count is missing when on iOS Safari. I'm having no problems with FireFox

 

[AxelCloris]

We've merged a few threads together for this issue. At this time, the issue appears to be impacting mobile and "tablet" resolutions. Our team is currently investigating a possible fix to roll out in a future update. Thank you everyone for your patience, and we appreciate the reports to help us squash these bugs.