Deskstop view issue
Reported by
satishka...@gmail.com,
Aug 15 2016
|
|||
Issue descriptionTHIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE! Device name:Xioami Redmi note 3 Android version:5.1.1 LMY 47V lollipop WebView version (from system settings -> Apps -> Android System WebView): Application:Google chrome Application version:52.0.2743.98 URLs (if applicable): Steps to reproduce: (1)keep 'Request desktop site' option untick(mobile view) (2)Enter any url (3)tick 'Request desktop site' option. It will show desktop version (4)go to any sub category on that page. (5)It will show desktop version. Then untick Request desktop site' option. It will show mobile view (6)now press back button. (7) Previous page will open with desktop view Expected result: On press back (step7) it should display mobile view, because we have set mobile view (step5) Actual result: On navigating back it is still showing desktop view.
,
Aug 15 2016
I believe that's intended result. "Request desktop site" will change everything in the navigation stack, not just the current page.
,
Aug 15 2016
Working as intended. The navigation stack explicitly records the state of the user agent when the user navigates.
,
Aug 16 2016
Hi, How could be it is intended functionality. If user untick ' Request desktop view' on any page that means he wants to mobile view throughout the session. On navigating back also he desire to see same view. Thanks & Regards Satish Kadam
,
Aug 16 2016
It's intended because that's how the feature was designed to work when it was implemented. The toggle records the state to (1) avoid confusing a user who is suddenly seeing different pages than they should when they start going backwards and (2) avoid extra network requests caused by having to reload the page with the user agent. Changing this behavior would be a feature request.
,
Aug 16 2016
,
Aug 16 2016
Hi team, Loads of thanks for resolving my query. Thanks & Regards Satish Kadam |
|||
►
Sign in to add a comment |
|||
Comment 1 by tobiasjs@chromium.org
, Aug 15 2016