Text doesn't get selected after tapping on select all option in "Pocket app".
Reported by
pshi...@etouch.net,
Mar 2 2017
|
|||||||||
Issue descriptionDevice name: Pixel XL/NOF26V,Nexus 5X/N4F26O,Htc Desire 630/MMB29M,Samsung Galaxy J5/MMB29M,Gionee F103/LRX21M WebView version: 58.0.3026.5 Application: Pocket Application version: 6.4.8.4 URLs : https://play.google.com/store/apps/details?id=com.ideashower.readitlater.pro&hl=en Bisect Information : Per-Version bisect information: Good build: 58.0.3018.0 Bad build: 58.0.3019.0 Regression range: https://chromium.googlesource.com/chromium/src/+log/58.0.3018.0..58.0.3019.0?pretty=fuller&n=10000 Steps to reproduce: (1)Launch 'Pocket' app,sign in with valid credentials (2)Open any article,Long tap for text selection and tap on select all (3)Observe Expected result: Text selection should be done properly after tapping on select all option. Actual result: Text doesn't get selected at all after tapping on select all option.
,
Mar 2 2017
Per-CL bisect information: Good commit:451580 Bad commit:451581 Culprit CL: https://chromium.googlesource.com/chromium/src/+/552ceb6deed19e86f89eb32b8fb3923217cefd7e tkent@ 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
,
Mar 2 2017
,
Mar 2 2017
> https://chromium.googlesource.com/chromium/src/+/552ceb6deed19e86f89eb32b8fb3923217cefd7e This is an intentional change. Can we contact a developer of Pocket app?
,
Mar 3 2017
what does the change do? It may affect many apps, how does the app developer fix the problem? Usually we don't want to break existing apps.
,
Mar 3 2017
An application needs to call Selection.removeAllRanges() before Selection.addRange(). I don't think the addRange() behavior change will break many applications. Applications rarely implement their own text selection features.
,
Mar 13 2017
A message from WebView bugcop: it seems there is an agreement in the Issue 353069 that this change is needed, yet this particular app does seem broken. tkent@, may I ask you to contact the app author and explain the rationale and what they need to do?
,
Mar 13 2017
,
Mar 13 2017
ok, I'll try to contact.
,
Mar 15 2017
Thanks for letting us know about this. Seems like an easy fix. Is there an easy way for us to test this? Some way to test our app on this new version?
,
Mar 16 2017
#10, Please follow https://www.chromium.org/developers/androidwebview/android-webview-beta . I think we'll push WebView beta based on Chromium M58 soon.
,
May 29 2017
,
Jul 19 2017
Issue doesn't repro on latest M60: 60.0.3112.72. Thanks! |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by battun@chromium.org
, Mar 2 2017Status: Available (was: Unconfirmed)