So when i type a comment (NOT A TOPIC) on a smartphone, touch-misalighnment occurs.
More info:-
https://community.infinite-flight.com/t/touch-mis-alignment-during-the-typing-mode-commenting/201711
AI-generated summary
Multiple users have reported issues with the editor cursor misaligning on Android Chrome, particularly on high-end devices. The issue is intermittent and not 100% reproducible, but evidence suggests it’s a real problem. zaidsal and others have reported the issue, and ljpp has provided a gif demonstrating the problem.
The cause is still unknown, but theories include CSS customizations, Chrome regression, and issues with ultra HD screens. Refreshing the browser temporarily resolves the issue, and no repro reports have been made on Firefox Android.
Iceman has confirmed that users on his Discourse instance are also experiencing the issue, and Cameron_D has suggested a possible connection to another Android issue with repro steps. Falco has reported that the bug can cause the cursor to register up to 200px up or down, depending on the direction of the trigger.
The discussion has been moved to https://meta.discourse.org/t/experiencing-a-lot-of-issues-replying-on-android/84086/42 for further investigation.
Can you repro here? We theorize that this is due to CSS customizations specific to the target site. You’ll need to give us repro steps here or on try.discourse.org
Ok I am testing here, seems fine here, will ask others to do it here.
It’s not consistent i might add, and on my iPhone 7+ it’s usually solved by just killing Safari/Discourse iOS App and relaunch.
Seb
IFC Moderator
Need repro steps here.
I’ve been getting intermittent misalignment on my Nexus 6 / Chrome. Usually fixed by causing the URL bar to appear again.
I’ve had it occur 2 to 3 times here on Meta in Chrome on my Pixel 2 XL. No repro, assumed it was something on my phone. Will pay closer attention.
Our staff is trying to hunt down a bug which seems to be somewhat similar to iOS 11 cursor misplacement, but this one is on Android Chrome. Discourse 1.9 stable.
Evidence:
What we know so far:
- Not 100% repro - pattern not found yet.
- Reported by multiple users/devices, but not by all. There is enough evidence to say that this is a real issue.
- Personally I have not seen this on a low-end Huawei tablet
- Could be related to ultra HD screens - reporters seem to have higher end devices?
- Originally we suspected the incident might have correlation with our high traffic hours, when messages are bursting in at a very high frequency. However our moderator recorded the video above during low/normal traffic hours, so maybe this is related to scrolling and overlays, similar to iOS Safari case.
- The 1st report about this came 22 days ago, but never before during our 2,5 years of operation. Chrome regression, maybe?
- So far no repro reports on Firefox Android. We have encouraged users to try this as workaround.
- Browser refresh seems help temporarily when this happens.
We could possibly try this iOS hack on Android as well, in case of flaky position fixed bugs. On iOS we hide the topic completely when you start editing so the positioning on the textarea is no longer fixed.
@Falco do you notice this issue as well?
Hi Guys,
I can confirm that I have users on my Discourse instance having this issue as well. I can’t get them to give specific repro steps.
I’m keeping an eye on this for the last few days and saw this. Maybe it’s related to CSS customizations?
Brother @iceman has reproed this on Try. The hard part is that this not 100% repro, but occurs rather randomly. But when it does, it is bad.
Could possibly be related to this:
Which does have repro steps now
Is very likely that it is related to the one reported by @Cameron_D. Not sure how to repro this 100% of times, will try with the method exposed by @codinghorror.
However, the reports I have are of not registering but it registering a little bit up. I’m gonna assume that’s because most of the thumb is blocked by the null area and it only registers the part that exceeds at the bottom.
Will keep informing.
The bug can make it register around 200px up or down, depends if you trigger the bug going up or down.
Let’s keep the discussion at Experiencing touch offset issues replying on Android - #42 by codinghorror