[Chrome Home] Back Button After Pressing Most Visited Tile Leaves Chrome |
|||
Issue descriptionChrome Version: current Chrome canary OS: Android What steps will reproduce the problem? (1) Open a new tab page. (2) Tap on a most visited tile. (3) On the new web site, decide I want to go somewhere else. Press back. (4) The nav panel opens, showing some of the NTP content, taking up half the screen. (This seems reasonable.) (5) I still want to see the actual NTP. Press back again. What is the expected result? (6) Either (a) the navpanel closes, showing the current web site. This would be gently guiding users to the idea that they have to interact with the navpanel to get where they want. In principle it's saying that it should suffice as an NTP-substitute. (b) the full page NTP displays. (This is my preferred option, as I'm not yet used to Chrome Home.) What happens instead? (6) Chrome closes and I'm left staring at the Android home screen.
,
Dec 6 2017
Zine triage: this seems like a Chrome Home issue, not NTP.
,
Dec 6 2017
Yep, I'm working on back button behavior PRD though I don't think it covers this scenario. How hard would it be to show the full page NTP on back?
,
Dec 6 2017
The PRD should cover this scenario if it doesn't already. Opening content from the NTP is one of the main use cases I laid out in our email thread. I also raised the question of opening to half-height vs full-height. For reference, here was my last email in the thread: It's likely too late for 64 given that feature freeze is Friday, but it'd be great to make a decision on how back press is handled so that I can circulate the design doc and get this in for 65. 1. Should the sheet be opened at half-height or full-height? Kingston said ideally it should open at the previous height, but full always could work too. My preference is to always open at full height. 2. If the content was opened from the NTP, what should happen on the first back-press? second-back press? There was some confusion around what was already implemented, but I think Kingston indicated that the first back press should open the bottom sheet over the current tab. The second back press would close the bottom sheet and close the tab (or possibly exit Chrome?). 3. If the content was opened in the middle of the navigation stack, what should happen on the first back-press? second-back press? Kingston's preference is open the bottom sheet over the current tab content on the first back-press. The second back-press would close the sheet and call Tab#goBack() to navigate to the previous URL.
,
Feb 6 2018
The Chrome Home experiment is being turned down, so closing this out. |
|||
►
Sign in to add a comment |
|||
Comment 1 by twelling...@chromium.org
, Nov 29 2017