Issues affecting android with Google Chrome

[Tommy]

Nov 19, 2024 16:42:38 GMT -8 Funkytown said:

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.

It's working now for me as well. Fingers crossed that Scott and crew got it fixed.

[aliciaadm]

Over here, it seemed to work for a second, but now I'm again experiencing the same problem. (Edge)

[Derek‽]

I can confirm that, as expected, the issue has spread and is impacting other Chromium 131-based browsers on Android, including the latest versions of Edge (131.0.2903.48) and Brave (1.73.89; Chromium 131.0.6778.69).

I can also confirm through testing that the same solution already proposed does fix the issue in these browsers as well. But leading a horse to water and all that.

The good news is that Chrome 131.0.6778.81 was released on November 19, and the issue appears to no longer be present. Anchor tags are once again containing the elements in place inside themselves. The other browsers should be updated within the next week, I would imagine. (Microsoft may very well be getting cute with their version numbers, or maybe they really are using an older build of 131 and there's no guarantee the next update of Edge will include the fix, be advised.)

[bigballofyarn]

Nov 22, 2024 13:14:40 GMT -8 Derek‽ said:

I can confirm that, as expected, the issue has spread and is impacting other Chromium 131-based browsers on Android, including the latest versions of Edge (131.0.2903.48) and Brave (1.73.89; Chromium 131.0.6778.69).

I can also confirm through testing that the same solution already proposed does fix the issue in these browsers as well. But leading a horse to water and all that.

The good news is that Chrome 131.0.6778.81 was released on November 19, and the issue appears to no longer be present. Anchor tags are once again containing the elements in place inside themselves. The other browsers should be updated within the next week, I would imagine. (Microsoft may very well be getting cute with their version numbers, or maybe they really are using an older build of 131 and there's no guarantee the next update of Edge will include the fix, be advised.)

My boyfriend is not having any issues in mobile Edge 131.0.2903.48 on his Android device, but I can only speak for him. I'm also not looking to argue or dispute your findings. I'm only passing along a message.

[Derek‽]

Nov 22, 2024 14:25:58 GMT -8 bigballofyarn said:

Nov 22, 2024 13:14:40 GMT -8 Derek‽ said:

I can confirm that, as expected, the issue has spread and is impacting other Chromium 131-based browsers on Android, including the latest versions of Edge (131.0.2903.48) and Brave (1.73.89; Chromium 131.0.6778.69).

I can also confirm through testing that the same solution already proposed does fix the issue in these browsers as well. But leading a horse to water and all that.

The good news is that Chrome 131.0.6778.81 was released on November 19, and the issue appears to no longer be present. Anchor tags are once again containing the elements in place inside themselves. The other browsers should be updated within the next week, I would imagine. (Microsoft may very well be getting cute with their version numbers, or maybe they really are using an older build of 131 and there's no guarantee the next update of Edge will include the fix, be advised.)

My boyfriend is not having any issues in mobile Edge 131.0.2903.48 on his Android device, but I can only speak for him. I'm also not looking to argue or dispute your findings. I'm only passing along a message.

Just to make sure everyone is on the same page, can you confirm that he's logged in while using the mobile view?

I'm posting from Edge 131 on my phone right now just to make sure I'm not crazy and the issue was present in this thread. Likewise, I just retested on my test forum and also reconfirmed the presence of the rendering issue and solution on my home test server.

Also not trying to argue or doubt him. While I still expect the issue to be patched away for everyone, it would be of interest to find out why some are affected and others apparently are not.

[bigballofyarn]

Nov 22, 2024 14:59:06 GMT -8 Derek‽ said:

Nov 22, 2024 14:25:58 GMT -8 bigballofyarn said:

My boyfriend is not having any issues in mobile Edge 131.0.2903.48 on his Android device, but I can only speak for him. I'm also not looking to argue or dispute your findings. I'm only passing along a message.

Just to make sure everyone is on the same page, can you confirm that he's logged in while using the mobile view?

I'm posting from Edge 131 on my phone right now just to make sure I'm not crazy and the issue was present in this thread. Likewise, I just retested on my test forum and also reconfirmed the presence of the rendering issue and solution on my home test server.

Also not trying to argue or doubt him. While I still expect the issue to be patched away for everyone, it would be of interest to find out why some are affected and others apparently are not.

He tested while logged in and only on my forum — no other forums. He was using mobile view.

The Chrome update isn't available to either of us though and we can't test that.

Edit: I don't have mobile Edge and didn't test it personally, but I was sitting next to him when he tested on his phone.