3 ms·
Hiding part of the path allows them to shrink the bar horizontally, which leaves more room for other content, such as chrome extensions.
by shadowgovt 6y ago
Hiding part of the path allows them to shrink the bar horizontally, which leaves more room for other content, such as chrome extensions.
- zrm 6y agoThe URL can already be longer than the screen to begin with, so they could still do that and show as much as will fit, showing the rest if you click on it. This is already what Firefox does.
- shadowgovt 6y agoBut from a UI standpoint, having a text box that is too small for its common displayed content is sloppy. If the path usually makes things too long, hide the path by default until the user asks for it.
- zrm 6y agoIt's only too small when it's too small. https://old.reddit.com/r/space/ https://old.reddit.com/r/space/ Fits fine and tells you at least three useful things that just "reddit.com" doesn't. https://old.reddit.com/r/space/comments/h8t50n/i_often_get_asked_if_people_can_use_my_images_as/ https://old.reddit.com/r/space/comments/h8t50n/i_often_get_a... Doesn't fit, but even truncated it still tells you the same useful things.
- shadowgovt 6y agoBut that's useful information that's told me redundantly by the page title and the banner at the top of the page also. I don't need the URL bar for that. In fact, using the URL bar for it assumes that the path has semantic meaning, which is not an assumption that the URL standard actually requires.
- zrm 6y ago> But that's useful information that's told me redundantly by the page title and the banner at the top of the page also. I don't need the URL bar for that. The page isn't required by anything to contain that information or to give it accurately. How do you distinguish example.edu/financial-aid/ from example.edu/~some-student/ ? > In fact, using the URL bar for it assumes that the path has semantic meaning, which is not an assumption that the URL standard actually requires. It doesn't assume anything, it just shows you the URL. If it has semantic meaning then you can see that -- which it commonly does.
- shadowgovt 6y ago> How do you distinguish example.edu/financial-aid/ from example.edu/~some-student/ That's an unrealistic example because no website worth its salt is going to let students put arbitrary content in the same domain as the financial aid system. That's a recipe for leaking cookies that contain session tokens, and displaying a full URL won't save a user. By the time you see the ~some-student in the URL bar, the security game is over.
- zrm 6y agoYou're making a lot of assumptions there. It could be that example.edu/financial-aid/ is just information and PDFs and doesn't have any sessions or cookies. Or the real financial aid system is on another domain, but a first time user doesn't know that, they're just looking at www.example.edu/~some-student/ which appears to be a financial aid page that Chrome only says is example.edu. Or any other case where the contents of the URL matters. How about example.edu/~some-student/ vs. example.edu/~a-different-student/ or example.edu/~your-professor/?
- shadowgovt 6y agoThat hypothetical naive first-time user is going to be as fooled by ~financial-aid, or by ~some-user/financial-aid. Showing the full URL path doesn't fix that risk scenario. The other scenario you describe, if the risk is someone intentionally deceiving users by cloning a page on the university network owned by someone else for deceptive purposes, is better solved by a university disciplinary hearing than by expecting every student to understand URL paths.