Chromestatus.com Sidebar Navigation Anomaly
Reported by
messagec...@gmail.com,
Sep 25 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: 1. Navigate to https://www.chromestatus.com 2. Intend to browse the changes landing in, say, 55 canary, and notice the sidebar menu indicating the page section currently in view. 3. Move to bring changes for 55 canary into view and disocver that this user action displays hysteriesis ( aka path-dependence ). If you scroll the main content pane down to the section for 55, the side bar indicates you are at 55 and you do indeed see the changes landing in 55. If instead you use the sidebar itself, not only as an indicator, but as a navigation menu, as is the common affordance, and click on the link for 55 canary the sidebar indicates you are at 55 canary, but the main content pane displays a different set of content. What is the expected behavior? The result of a navigation should not depend on the path one took to get to the navigation. So both clicking on the sidebar and scrolling the main pane should produce the same result. What went wrong? They don't. Clicking on the sidebar actually updates the search field with this value '=55' and then yields all the changes that have the term '55' anywhere in their text. This is non-identical with what happens when you simply scroll the main content pane down to the 55 section. This non-identicality is despite the navigation bar, trusted aide that it is, indicating you have arrived at the same place. Did this work before? N/A Chrome version: 53.0.2785.116 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 Is this a 'feature' not a bug?
,
Sep 25 2016
If I remember correctly, search filtering was added several months ago and never worked properly since then.
,
Oct 5 2016
Thanks for the report. We're tracking this in the site's github issue tracker: https://github.com/GoogleChrome/chromium-dashboard/issues/367 Feel free to add a comment over there.
,
Oct 5 2016
|
||
►
Sign in to add a comment |
||
Comment 1 Deleted