So when i type a comment (NOT A TOPIC) on a smartphone, touch-misalighnment occurs.
More info:-
So when i type a comment (NOT A TOPIC) on a smartphone, touch-misalighnment occurs.
More info:-
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:
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?
@iceman just reported that this still occurs with Discourse 2.0.1. This is a tough nut to crack, as triggers and repro pattern is unclear.
@iceman, got any new intel how to repro this?
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