Issues affecting android with Google Chrome

[🎶Sossity🎶]

Please be aware that the current issues affecting android mobile users on Google Chrome appears to be emanating either from the latest updates from Google Chrome or from a bug in its software.
Either way, there’s nothing we can do here on ProBoards support except to advise using another mobile browser for the forums or select desktop mode until Google updates or resolves this issue.

support.proboards.com/thread/677861/chrome-on-android

support.proboards.com/post/7361464

[comet52]

I'm having the same issue on both Pro boards forums that I read. And it's happening with Chrome and with DuckDuckGo browser as well.

[Derek‽]

I have located the source of the incompatibility, solved it, and submitted the solution to Scott to be passed to management for consideration of possible implementation.

The issue is present in Chromium 131 but not 133 (unsure of 132, untested), and thus I'm more and more inclined to believe this sudden incompatibility will be fixed in a future stable public release of Chrome. The timetable for that is uncertain, however. It could just as easily be three months as it could be a week.

Other browsers may be affected! All major browsers are Chromium-based. As others update their rendering engines to 131, the issue can spread to them as well. This could still be affecting some users well after others are in the clear.

[bigballofyarn]

Nov 16, 2024 18:55:33 GMT -8 Derek‽ said:

I have located the source of the incompatibility, solved it, and submitted the solution to Scott to be passed to management for consideration of possible implementation.

The issue is present in Chromium 131 but not 133 (unsure of 132, untested), and thus I'm more and more inclined to believe this sudden incompatibility will be fixed in a future stable public release of Chrome. The timetable for that is uncertain, however. It could just as easily be three months as it could be a week.

Other browsers may be affected! All major browsers are Chromium-based. As others update their rendering engines to 131, the issue can spread to them as well. This could still be affecting some users well after others are in the clear.

Do you mind if I share your findings on my forum as a direct quote, attributed to you?

[Derek‽]

Nov 17, 2024 7:05:07 GMT -8 bigballofyarn said:

Do you mind if I share your findings on my forum as a direct quote, attributed to you?

Not at all, go for it.

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.

[marcoducatti]

is this something moderators should be implementing manually or will this be integrated by proboards staff?

[Scott]

Nov 18, 2024 10:22:52 GMT -8 marcoducatti said:

is this something moderators should be implementing manually or will this be integrated by proboards staff?

This is not something that can be implemented manually since it involves the mobile template.

[lolman]

It's now doing the same thing with Brave browser. It was working for me before.

[esdda2]

I am having also the same issue with some members !!

[aliciaadm]

Same issue here on Android Chrome AND Edge.

[comet52]

Installed Edge, which worked for a couple of days, now it has the same issue. I think I ran out of browsers.

[Scott]

Firefox is still an option. It's not Chromium-based.

[Funkytown]

Nov 18, 2024 10:29:36 GMT -8 Scott said:

Nov 18, 2024 10:22:52 GMT -8 marcoducatti said:

is this something moderators should be implementing manually or will this be integrated by proboards staff?

This is not something that can be implemented manually since it involves the mobile template.

Is this something that is being considered, or do we all have to switch to Firefox?

Just trying to figure out what to tell everyone. It's driving everyone batty! lol.

[Scott]

Funkytown - yes it's something we're actively looking at.

[Funkytown]

Nov 19, 2024 11:52:04 GMT -8 Scott said:

Funkytown - yes it's something we're actively looking at.

It's working now! Is that because of you guys?

Either way, I hope it's working for good now and this isn't some fluke. lol.