Issue metadata
Sign in to add a comment
|
Cursor and handle appear misplaced when forwarding mail in Yahoo Mail
Reported by
ngo...@etouch.net,
Aug 8 2017
|
||||||||||||||||||||||
Issue descriptionDevice name: Pixel XL/(NJH47D), Nexus 5X/(NRD90R), Samsung Galaxy J2/(LMY47X), Micromax Q372/5.1 (LRX21M), Sony Xperia XA/6.0(33.2.B.2.93), ASUS_Z010D /6.0.1(MMB29P), Htc Desire 630/6.0.1(1.00.400.3), Panasonic Eluga Turbo/5.1(LMY4&D), Gionee S6s (Mali-T720)/MRA58K Application: Yahoo Mail Application version: 1.0 WebView version: 62.0.3178.0 Steps to reproduce: 1. Launch Yahoo Mail > Inbox > Open a particular mail from inbox (Refer screen record). 2. More options > Click on forward > Click on the area as shown in the screen record. 3. Observe Frequency : 3/3 This is a regression issue broken in 'M-61' and below is the bisect range. Good build: 61.0.3129.3 Bad build : 61.0.3132.0 Bisect Range: https://chromium.googlesource.com/chromium/src/+log/61.0.3129.3..61.0.3132.0?pretty=fuller&n=10000 Actual result: Cursor and handle are misplaced/separated. Expected result: Cursor and handle should be together.
,
Aug 8 2017
,
Aug 9 2017
Per-CL bisect information: Good commit:479263 Bad commit:479264 C 605.255s Main You are looking for a change made after 479263(GOOD), but before 479264(BAD). Suspect CL: https://chromium.googlesource.com/chromium/src/+/4a043e477b4857645c2f73583ea147b318fb40a4 yosin@ Might be it looks like this issue is related to your change. please look into once, if its not related to your change please reassign to me. Thanks!
,
Aug 9 2017
Note:Issue can observed on only on Facebook friend suggestions mail. Thanks
,
Aug 9 2017
The patch mentioned in #c3 fixed buggy behavior of Chrome. Clients should not depend on buggy behavior.
,
Aug 9 2017
Sounds like this is still a bug though, even if the CL in c#3 fixed something else. yosin@, could your CL have exposed an already existing bug? If the bug still exists, we probably need more investigation. Cc'ing some text selection people. If I'm mistaken, please go ahead and close this again.
,
Aug 11 2017
As yosin@ mentioned in #5, now it is app's issue to use boggy behavior of Chrome, yosin@ could confirm and close the issue if it is true.
,
Aug 11 2017
Ah, sorry--I misunderstood. Yes, feel free to close. If we're sure this is an app bug, let's do developer outreach. I'm assuming the app's package name is com.yahoo.mobile.client.android.mail (ngosar@ please confirm). If that's correct, go/da-lookup says that pmatthews@ is the DA, so we should reach out to him.
,
Aug 16 2017
ntfschr@ Yeah this is correct package name: com.yahoo.mobile.client.android.mail Thanks!
,
Aug 16 2017
Thanks, battun@. yosin@, would you be able to reach out to pmatthews@google.com describing the app bug and ask how best to notify the app developers?
,
Aug 21 2017
Hi pmatthews@, could you contact to Yahoo Mail app team to fix their app to align with M60+? Before the patch in #c3, Chrome's behavior was undefined, Chrome returned unexpected value. Thanks!
,
Aug 21 2017
Opening this up to the public, since there's nothing confidential here. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by battun@chromium.org
, Aug 8 2017Status: Untriaged (was: Unconfirmed)