This makes a bold assumption that all sites would implement their directory structures in this manner. Windows Explorer can make the assumption because this is how file stores are structured, a child can have only one parent. Many sites do not have a linear or tree-style browsing structure; to make this work, the website would have to provide some sort of file which detailed every possible branch available, and for some sites, like Amazon.com, this is impossible and the structure changes based on the users browsing behavior.
Although it may be possible for sites to identify themselves as being able to support such a navigation tool, that would lead to an inconsistent browsing experience; the 'up' button works on this site but not another. Imagine if you will a website which uses a content management viewer app; this website may never change which page you physically access, but the content may change based on parameters, how would Chrome be able to determine where to go if the page never technically changes? Your example of bread crumbing is a perfect reason why you shouldn't implement something like this at the browser level; you can remove any layer of the navigation at any time from sites such as Newegg, whereas an 'up' button would only be able to remove the lowest level. These sites work more like search filtering than they do navigational pathing. I believe a feature such as this is best left for the web site to implement and not the responsibility of the browser. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
