[MD History] Invalid pages names are allowed in route
Reported by
rk...@etouch.net,
Feb 27 2017
|
|||||
Issue descriptionChrome Version: 58.0.3025.0 Revision 636f441be350ec76e73b4e4f407bf8a7e86984fd-refs/heads/master@{#453134} OS: Windows (7,8,10), Mac (10.11.6,10.12.1), Linux (14.04 LTS) What steps will reproduce the problem? (1) Launch chrome, navigate to chrome://history page. (2) Click on omnibox and 'Copy' url then 'Paste' it 2 times. (3) Hitt Enter and observe omnibox url. Actual: Omnibox url is not correct for chrome://history page. Expected: Omnibox url should be correct for chrome://history page. This is a regression issue, broken in 'M-58', will soon update the other info: Good Build: 58.0.2997.0 Bad Build: 58.0.2998.0
,
Feb 28 2017
This is really low priority. We only really support a handful of URLs, and so long as any invalid URLs (like the one in the original report) don't break the page, I'm happy. The original bug can be rephrased as: 1. Navigate to chrome://history/foo Expected behavior: 'foo' should be stripped from the URL. The history-list should display results, and the sidebar should highlight 'Chrome History'. Actual behavior: 'foo' is not stripped from the URL. The history-list displays results, but the sidebar does not highlight any item as selected. Fixing this will probably require adding a list of valid pages into router.js
,
Mar 3 2017
,
Mar 20 2017
Able to reproduce the issue on mac os 10.12.3 using chrome canary M59 #59.0.3046.0 , following steps mentioned in comment #2. Gentle ping , to get an update on this. Thanks!
,
Sep 8 2017
Reassigning to calamity. Realistically, I'm not sure that we'll ever fix this. Feel free to WontFix.
,
Sep 12 2017
I can live with this. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Feb 27 2017Owner: tsergeant@chromium.org
Status: Assigned (was: Unconfirmed)