The three buttons that pop up after selecting text on a mobile browser do not work when clicked

Ondersteuning
1

Usually on Discourse, after selecting text, a pop-up window appears with a row of buttons including “Quote” and “Copy Quote”.
Recently, it has been found that on some mobile browsers, when these buttons are clicked, they simply disappear without bringing up the reply window or writing to the clipboard. Through testing on a self-hosted Discourse instance and on Meta, the issue is consistent. Changing the UA to use desktop view to operate still does not make them work. Checking browser settings to confirm that ad blocking and other options have been disabled shows no effect.

Currently, one problematic sample browser has been identified and the following tests were performed on it:
On @Arkshine’s https://arkshine.github.io/discourse-features-test/, all three test results were Support.

373017bb054739fdc8a35d35b31eb8d2
373017bb054739fdc8a35d35b31eb8d21080×1744 84.1 KB

Through @supermathie’s https://www.supermathie.net/reflect/headers, the following result was obtained:

accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
accept-encoding: gzip, deflate, br, zstd
accept-language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
connection: keep-alive
host: www.supermathie.net
sec-ch-ua: "XiaoMiBrowser";v="135", "Not-A.Brand";v="8", "Chromium";v="135"
sec-ch-ua-mobile: ?1
sec-ch-ua-platform: "Android"
sec-fetch-dest: document
sec-fetch-mode: navigate
sec-fetch-site: none
sec-fetch-user: ?1
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Linux; U; Android 15; zh-cn; 23049RAD8C Build/AQ3A.250226.002) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.7049.79 Mobile Safari/537.36 XiaoMi/MiuiBrowser/20.12.1030209
x-miorigin: s

The browser kernel version does not appear to be lower than the minimum version required for the target.

2

Can you repro this in safe mode? Does this happen here on Meta?

3

Yes, for example, by directly appending /?safe_mode=no_themes,no_plugins to the URL of the page (Meta), the test result remains unchanged.

4

Is that this browser?

I tried it on an Android 15 virtual device - here is Chrome properly working:

image
image613×1372 158 KB

and Firefox:

image
image613×1372 144 KB

but when I try and use the Mi Browser, if I navigate to any website it immediately crashes:

image
image613×1372 20.9 KB

(screenshot taken immediately before crash)

It may be the Chromium rendering engine, but they’ve evidently done something to their version that makes these buttons not work. These problems are likely best reported to the respective developer via the browser’s feedback mechanism.

2 likes
5

To ensure the accuracy of the conclusion, I have found a browser sample from another user’s feedback, with the parameters as follows.

accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/wxpic,image/sharpp,image/apng,image/tpg,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
accept-encoding: gzip, deflate, br
accept-language: zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7
connection: keep-alive
host: www.supermathie.net
q-ua2: QV=3&PL=ADR&PR=QB&PP=com.tencent.mtt&PPVN=19.9.5.5035&TBSVC=45001&CO=BK&COVC=048603&PB=GE&VE=GA&DE=PHONE&CHID=0&LCID=25749&MO= FIN-AL60a &RL=1084*2302&OS=12&API=31&DS=64&RT=64&HM=1&HMVN=3.0.0&REF=qb_0&TM=00
sec-ch-ua: "Not A(Brand";v="99", "Android WebView";v="121", "Chromium";v="121"
sec-ch-ua-mobile: ?1
sec-ch-ua-platform: "Android"
sec-fetch-dest: document
sec-fetch-mode: navigate
sec-fetch-site: none
sec-fetch-user: ?1
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Linux; U; Android 12; zh-cn; FIN-AL60a Build/HUAWEIFIN-AL60a) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/121.0.6167.71 MQQBrowser/19.9 Mobile Safari/537.36 COVC/048603

Perhaps you could try to see if it also exhibits this issue.

6

We could track down these browsers and try and duplicate the problem, but even if we did the answer would likely be “Yep, the browser must be doing something wrong.”

I recommend these users install a supported browser such as Chrome, Chromium, Firefox, or Edge.

2 likes
7

Yeah, we have already conducted tests using mobile browsers such as Edge and the results were good. :slightly_smiling_face:
As for the new sample mentioned above, because the initial sample encountered a crash issue as you mentioned in your previous reply, I found it and hope that this can help in conducting a normal analysis to confirm the conclusion.

8

com.tencent.mtt (assuming that’s the correct package name) isn’t published to Google’s store so I can’t even test it.

Unfortunately, spending time doing anything beyond installing the browser from the store and trying it to see what happens isn’t viable.

2 likes