|
|
Post by Bill in the rain on Nov 19, 2024 1:39:21 GMT
Switching to the desktop version of the site might be a temporary fix, though iirc that means very small text and buttons on mobile.
|
|
rftp
New Member
Posts: 692
|
Post by rftp on Nov 19, 2024 7:48:52 GMT
Now doing the same thing on Brave (Chromium based).
No site controls working whatsoever on mobile. Presumably this is Google fucking about with their browser code to try and stop people blocking ads.
|
|
|
|
Post by Trowel 🏴 on Nov 19, 2024 13:33:52 GMT
Was playing up for me this morning on Chrome v131 on mobile, but now seems to be OK?
|
|
|
|
Post by dfunked on Nov 19, 2024 13:42:43 GMT
Still fucked for me. It seems to mainly be anything at the top of a page. If you scroll past that then most functionality should be there, apart from the settings button on your own posts.
|
|
deez
New Member
Posts: 716
|
Post by deez on Nov 19, 2024 13:51:23 GMT
I use Opera and it's fine. I just got a new phone and thought I'd give Chrome another try and I wasn't impressed.
|
|
|
|
Post by quadfather on Nov 19, 2024 15:18:21 GMT
Still fucked for me. It seems to mainly be anything at the top of a page. If you scroll past that then most functionality should be there, apart from the settings button on your own posts. Yeah same here. Just the top area fucking up. I'm on an Samsung Android galaxy and using Chrome. I had a system update about a week ago, but I've only noticed the issue today and I'm on this site daily. |
|
BeetrootBertie
Junior Member
Beets the hell out of me
Posts: 1,166
Member is Online
|
Post by BeetrootBertie on Nov 19, 2024 15:42:37 GMT
Apparently it's a CSS issue with the mobile template for the boards that's not behaving with the 131 update. From the support forum by a user called Derek: "For those curious: it's a CSS issue at play. The "post options" buttons are illusions hiding invisible <select> elements. To achieve the blue glow effect, the buttons are wrapped in <a> tags. It's perfectly valid to do this, but anchors aren't containers, and the <select> tags are breaking out of their parent elements. The CSS styling rules tell this class of <select> to take up their entire parent, but their parent anchors aren't supplying boundaries. As such, these invisible input controls are taking up the entire page. They're stacked on top of each other with the first post's <select> element on the bottom and the last on top. Users are completely unaware that they're tapping these inputs because of their invisible styling. The solution is to replace each <a> with <div> and everything (minus the glow effect we don't even notice because our sausage thumbs are in the way) goes back to normal." support.proboards.com/thread/677873/issues-affecting-android-google-chrome |
|
Lukus
Junior Member
Posts: 2,700
|
Post by Lukus on Nov 19, 2024 17:06:19 GMT
So they know the solution. Do a solution then Rodger Pro Boards
|
|
|
|
Post by baihu1983 on Nov 19, 2024 19:36:55 GMT
Working fine now
|
|
|
|
Post by dfunked on Nov 19, 2024 19:40:18 GMT
Huh, so it is... Attaboy, Rodger Proboards!
|
|
Lukus
Junior Member
Posts: 2,700
|
Post by Lukus on Nov 19, 2024 19:54:44 GMT
I'm gonna take credit for that
|
|
|
|
Post by stixxuk on Nov 19, 2024 20:29:53 GMT
Still broken for me :/
|
|
rftp
New Member
Posts: 692
|
Post by rftp on Nov 19, 2024 20:34:29 GMT
And me. But meh, Firefox works.
|
|
mrpon
Junior Member
Posts: 3,732
|
Post by mrpon on Nov 19, 2024 21:23:18 GMT
Yep all good here. S22 Chrome.
|
|
|
|
Post by stixxuk on Nov 19, 2024 21:29:58 GMT
Fine on Chrome (on Android, Pixel 8). Not on Edge.
|
|
|
|
Post by Bill in the rain on Nov 20, 2024 1:23:36 GMT
Sounds more like they've updated Chrome to fix whatever they did, but all the other browsers that use Chrome under the hood are still rocking the broken version.
|
|
