Posting bounce-back from edit screen (mobile)

[altenbach]

I don't think I have an app to record the screen. Any recommendation?

[LiliMcDonald]

According to this recent How-To-Geek article, AZ Screen Recorder is a good option for Android.

[altenbach]

(using DU recorder) All I do here is press [reply] and then touch the edit window on the next page. The rest is automatic, including the scroll down to place the grayed buttons into view.

[LiliMcDonald]

Thank you! This is helpful.

[altenbach]

Quick summary of some key points:

• When on the edit window, any touch of the screen acts like a "browser back" command during the first (many!) seconds of opening the edit window.
• This happens when composing a new message or when editing an existing message
• The only way to prevent it is to wait a (very!) long time before putting the finger down anywhere on the edit window. When I say a long time, I mean it! In recent days I waited quite a few seconds and many times the bug still got triggered. Now I wait at least 10 seconds or more (not easy to do for a impatient users! :().
• This is 100% reproducible!

Android 6.0.0, chrome browser 60.0.3112.66 (beta) or chrome 59.0.3071.125 (released). Both version are plain vanilla. No unusual extensions or security settings. XT1095, (near plain android, not rooted, no vendor skin)

[LiliMcDonald]

Thanks for the notes. I have passed along this information.

[altenbach]

On a side note, notice that the video insert tool is missing from the mobile editor (~8 seconds into the video). That would have saved me some time here.

(I did the recording and youtube upload on mobile and did not have access to a desktop for a while.)

[LiliMcDonald]

Hi Christian,

Do you see any difference if you clear the cache/cookies of the browser?

Thanks,

Lili

[altenbach]

Yes, I just signed out of chrome, cleared everything to the beginning of time, signed back in, and the problem is still there. (The first time I tried to answer here just now, it kicked me back to the thread) 😞

[Blokk]

I have also still this problem, despite clearing Chrome browser cache.

The difference in my case is the affected time interval: in my case it is only a couple of seconds roughly after tapping onto the "Reply" button, when this bounce back occurs. I still believe the reason is that, during page load, even if you think/see that you tap into the text field, actually the tap fires above the "Cancel" button! 

I have no idea why altenbach has a much bigger time interval? Maybe it depends also on the processing speed of the phone hardware / actual bandwidth/ping ???

Anyway, for the record, i put here my video which shows such bounce back. Note that, the first part of the video shows the effect when i do not wait until the page is fully loaded, thus it is more likely this problem happens on my phone. The second part of the video shows just that, if I wait enough to the page fully loaded then (usually?) i have NO bounce back bug... The last cancel action in the video is intentional, the first is by the "bounce back bug".

Maybe the web designer team could disable that cancel button until sensing that text field edit really started? I have no idea if such possible, but could help!

The video:

https://youtu.be/rD8FO6DOZOQ