I would say it falls under the category of "plugins", as a plugin's functionality does not need to "work" with every site, whereas "default" browser chrome sorta does.
Thus, it is a browser function (it's part of the chrome, so websites should not be able to alter it to that extent), but not one that should be considered a feature request for the main codebase. I agree that most of these websites have developed different methods for content navigation which don't require an "up" button, but I design my sites hierarchically and rarely (if ever) use "up" navigation - I just have "home" links everywhere. Also, when I was writing directory listings in a rough .php script (which kinda works), the "up" functionality was the most difficult to implement securely (php would inherently allow you to visit http://mysite/../../../../../../../../../ and that's not very good) - I can't remember the working solution, but I know an "up" button would have been pretty darned useful. If it is implemented as a plugin to chrome, I might spend the time rewriting my solution and writing/finding a plugin for firefox so I can depend on both plugins to... I'm rambling. Point is, this is useful functionally but impractical to try to implement web-wide. It should be site-wide implemented, which means it falls under the category of "plugin request". --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
