Mobile Layout Exploded

Undead Scottsman

Mobile version of the forum currently looks like this:

I'm using Chrome on a Samsung Galaxy S9

Fullsite works fine

EDIT: Okay, the image should be working now. Unfortunately it's huge and I dunno why.

Man in the Mists

Same here. Firefox mobile (68.4.1) on a Samsung Galaxy J7 Star, Android version 9.

Tube

Happening to me too, I'll file a bug if it's not fixed within an hour by itself

Feral

If it helps at all, the mobile site loads up

https://forums.penny-arcade.com/static-asset/cl40013/asset/less/mobile/style-44774d71.css?v=4.0-2020.003.5e4c38dc

the contents of which are just

/* Compiling, please wait */

Removing the version number and going to https://forums.penny-arcade.com/static-asset/cl40013/asset/less/mobile/style-44774d71.css

results in a properly compiled CSS starting with

/* Date: Wed, 19 Feb 2020 22:36:48 +0000
 * ETag: 44774d71
 * Original Format: less
 * Compile Time: 0.45s
 *
 * /themes/lithemobile/less/style.less
 */

skeldare

It was working fine for a bit but now seems to have broke again

Opty

I'm surprised at how usable the boards are in this broken state

Gnome-Interruptus

Every thing is there, just not where you might expect or how it usually looks.

My favourite is how all the agree and awesome have full size avatars

Tube

Please provide browser and device info

Reznik

Device: Samsung A5, Android 8.0.0

Browser: Ecosia 69.0.3497.128

Weaver

Still way broken here.

Galaxy Note 10+, Chrome

SmokeStacks

Same here. Note 10+, Android 10, Chrome

Looks fine on Samsung's browser though, if that helps.

Edit: 79.0.3945.136

Dehumanized

Broken on iphone X, safari in latest iOS

Tube

version numbers if possible please

Weaver

Chrome 80.0.3987.99

kime

iPhone 7 Plus
iOS 13.3.1
Chrome 80.0.3987.95

Aridhol

Samsung 9s+
Chrome 80.0.3987.117

m0hj

Pixel 4 XL
Edge version 44.11.4.4140

Burtletoy

Had this draft this morning, but it started working fine so then decided not to post. Now it's all broken again, so I'm posting the draft

It's working now for me, but was messed last night and this morning.

OnePlus 5t
Firefox 68.5.0

kime

It's still broken for me. I've not noticed any periods of not-brokenness

Moridin889

S7 edge

Chrome 80.0.3987.99

Opty

Seeing it on a Samsung A50 with Chrome, v80.0.3987.87
Edit: Updated to v80.0.3987.117 and it's still broken

Mvrck

Samsung Galaxy S6
Chrome 79.0.3945.136
Firefox 68.4.2
Android 7.0

Lavender Gooms

Moto G6
Android version 9
Chrome 80.0.3987.117

Jebus314

Still borked for me.

iPhone 6se
iOS 12.4.1, safari 12.1
And also iOS 13.3, and safari 13

Gnome-Interruptus

Was working for me between midnight and 8am and has broken again

Though now I’m wondering if that’s because I was on wifi and not data

iPhone XR with safari browser

Tube

is there anyone reading this thread who's like "huh, never happened to me even once" and it's looked fine for the last few days?

Powerpuppies

Yes

Iphone 11 safari, on wifi the whole time if that matters

Feldorn

iPhone SE
iOS 13.3.1
Safari
Firefox 22.0 (17157)

Broken whether on data or wifi.

Tube

Powerpuppies wrote: »

Yes

Iphone 11 safari, on wifi the whole time if that matters

Could you give me your browser version?

Powerpuppies

Tube wrote: »

Powerpuppies wrote: »

Yes

Iphone 11 safari, on wifi the whole time if that matters

Could you give me your browser version?

doesn't seem to have one. If I'm on ios 13.3.1 I guess I'm on safari 13?

crimsoncoyote

Tube wrote: »

is there anyone reading this thread who's like "huh, never happened to me even once" and it's looked fine for the last few days?

Hi yes me.
Pixel 2 XL, Android 10
Chrome 80.0.3987.117

kime

Right now, as of posting this (don't know when it started exactly), my layout is correct on mobile (same versions I posted above)

It has exploded again.

Feral

Two days ago, when I posted my comment about CSS above, I was able to reproduce the problem using Chrome on Windows 10, in F12 Developer Tools, and Device Mode, by setting different mobile layouts. (I cleared my cache and reloaded each time I changed layouts.)

I think that means it was responding to either the device resolution or the user agent to identify whether to feed up the broken CSS.

Today, I'm trying that and it no longer reproduces the problem. That said, I am using a different computer today than I was two days ago.

FWIW, I'm still seeing the problem on my phone:

OnePlus 5
Screen res: 1080p
OS version: Android 9 (Oxygen 9.0.9)
Browser: Brave, v 1.5.4

NFyt

Tube wrote: »

is there anyone reading this thread who's like "huh, never happened to me even once" and it's looked fine for the last few days?

+1 for haven't noticed any mobile explodings

Chrome 80.0.3987.99
Android 10 on a pixel 2

J-bob

Currently broken for me.

Chrome 80.0.3987.117

Android 9 on a Samsung Galaxy s8

Tube

NEO|Phyte wrote: »

Tube wrote: »

is there anyone reading this thread who's like "huh, never happened to me even once" and it's looked fine for the last few days?

+1 for haven't noticed any mobile explodings

Chrome 80.0.3987.99
Android 10 on a pixel 2

Could you update your chrome and see if that breaks it maybe? This is a weird request I know.

Burtletoy

It's working now for me, again

Undead Scottsman

Still busted for me,

Samsung Galaxy S9 running Android 10

Chrome v80.0.3987.117

Burtletoy

Burtletoy wrote: »

It's working now for me, again

It was working for me at the store, while I was on Network signal, then got home and wasn't working on wifi.

Turned off WiFi and it's fixed again.

Undead Scottsman

Burtletoy wrote: »

Burtletoy wrote: »

It's working now for me, again

It was working for me at the store, while I was on Network signal, then got home and wasn't working on wifi.

Turned off WiFi and it's fixed again.

Sadly that didn't work for me.

Feral

Feral wrote: »

Two days ago, when I posted my comment about CSS above, I was able to reproduce the problem using Chrome on Windows 10, in F12 Developer Tools, and Device Mode, by setting different mobile layouts. (I cleared my cache and reloaded each time I changed layouts.)

I think that means it was responding to either the device resolution or the user agent to identify whether to feed up the broken CSS.

Today, I'm trying that and it no longer reproduces the problem. That said, I am using a different computer today than I was two days ago.

FWIW, I'm still seeing the problem on my phone:

OnePlus 5
Screen res: 1080p
OS version: Android 9 (Oxygen 9.0.9)
Browser: Brave, v 1.5.4

I just cleared my browser cache on Brave and the layout is no longer broken.