New issue
Advanced search Search tips

Issue 883673 link

Starred by 2 users
Status: Unconfirmed
Owner: ----
Cc:
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Webview history doesn't remove entry when back done with history.go(-1)

Reported by ktpiyus...@gmail.com, Sep 13 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Open any webview link
2. push into history twice
3. execute history.go(-2)

What is the expected behavior?
After the execution of history.go(-2), by pressing back once it should close the webview

What went wrong?
3 times back is required to be pressed i.e. even after executing history.go(-2) history stack had 3 items.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 68.0.3440.106  Channel: n/a
OS Version: OS X 10.12.6
Flash Version:

Comment 1 by dtapu...@chromium.org, Sep 13

Components: Platform>Apps>BrowserTag

Comment 2 by lfg@chromium.org, Sep 13

Labels: Needs-Feedback
Is this on Android webview?

Comment 3 by krajshree@chromium.org, Sep 14

Labels: Needs-Triage-M68

Comment 4 by ktpiyus...@gmail.com, Sep 14 

Yeah checked on multiple android webviews
Project Member

Comment 5 by sheriffbot@chromium.org, Sep 14

Cc: lfg@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by lfg@chromium.org, Sep 14

Components: -Platform>Apps>BrowserTag Mobile>WebView
Labels: -OS-Mac OS-Android
Thanks for the feedback, tagging with the correct OS and component for triage.

Comment 7 by chelamcherla@chromium.org, Sep 17

Labels: Needs-triage-Mobile

Comment 8 by chelamcherla@chromium.org, Sep 17

Labels: Triaged-Mobile Needs-Feedback
@ktpiyush91: Could you please provide test URL to test this issue from our end along with screencast, this would help in better triaging of the issue. Also please check the issue on latest stable #69.0.3497.91 and if reproducible provide device details and android version.

Thanks!

Comment 9 by chelamcherla@chromium.org, Sep 17

Labels: -Triaged-Mobile WV-Triaged
►

Sign in to add a comment