Please see videos and photos below to understand the issues.
https://mega.nz/file/QiR3yIIb#dTJ-xkM6YixqVLP91167hrJjzdgbZQ9ksDyJKW9TuZQ
Unable to select the composer to enter text
https://mega.nz/file/47w1gbjb#cyKJz1inZOQ8_32LpuTaRiuD0wTl4gEizHFVZkP_G28
Browser tools obscuring the select to quote feature.
Horizon Solarised theme. (Happens on a couple of other themes too) On Android 15. Issue on Samsung Internet and Vivaldi. OneUI 7
Is this normal? Selecting texts not only hides everything but also shortens the “blue” space but it doesn’t alter all the selected texts either ie. if you cut/copy even if it covers the whole text it doesn’t cut/copy all the selected texts.
User 1:
Theme: core
OS: Android 16
Browser: Chrome on android
I can’t select text to quote. This occurs frequently but not always. When I press and hold on some text, the mobile vibrates; that’s all. No text gets selected.
User 2:
+100 to this. This appears to have increased and is happening more and more. I am on Cromite.
User 1:
Yep still there on iOS 26.1.
And sometimes all the buttons are are also displaced, so you need to tap slightly below where the buttons are supposed to be, it’s pretty horrendous to use to reply and stuff sometimes lol. Even more so because adjusting text selection while trying to quote something also doesn’t work reliably. Really not sure what’s so wrong with this specific PWA.
User 2:
Tried on Safari, the problem still exists. Tried on Firefox and it’s fine.
The easiest way to replicate it:
Start typing any message, minimize the editor, open it again, and the cursor is displaced from the actual text being written.
User 3:
That’s probably a different issue, and definitely not difficult to solve, just depends on how discourse is coded.
The issue is specifically on Safari on iOS, after you go through the steps I mentioned. The cursor appears at a false location. The cursor appears below its true location. When I start typing, the text actually appears above the blinking cursor.
I tried on Firefox too, no issues there. So I believe this is an issue with discourse on Safari.
