4 ms·
> I really dislike any attempt to modify strings like this. I find it invariably causes problems in edge cases. What if a site handles slashes differently to ho
by sorenjan 6y ago
> I really dislike any attempt to modify strings like this. I find it invariably causes problems in edge cases. What if a site handles slashes differently to how Google expects?
I think it would have to be some standard format that websites use, not just string manipulation in the browsers. And certainly not some Google dictated feature! For the same reason, each part would have to be navigable on these sites, to work as I described. There's various possible solutions, like meta tags or some manifest like breadcrumbs.jsonld mentioned in another comment.
The fact that Windows Explorer doesn't show the full URL in special folders is a separate issue, I only mentioned it for the breadcrumbs example.
- wyattpeak 6y agoIf you're talking about something other than manipulating the URL, I don't understand what problem you're solving. Sites which believe that breadcrumbs would be helpful for navigation already have breadcrumbs, I see no reason to force it on everyone else. But I disagree with you that not showing the full address in Windows Explorer is a separate issue. In my experience loss of edge-case functionality is a core aspect of changing interfaces. Maybe in another world the address would be preserved, and my use case would still work. But someone else's unusual use would not.
- sorenjan 6y agoInstead of manipulating the URL it would replace it, and instead of each site doing it their way it would be handled by the browser in the browser UI. Sites can implement their own back button too, doesn't mean that's where it belongs. Think about how Powershell use objects instead of text to chain together commands. The address isn't just text, it's structured data, why not treat it as such and make it more useful?