Humans can't read URLs. How can we fix it?
Jake leads this HTTP 203 episode with his reflexions about current URL display practice in browsers, and how it could be improved, at least for security.
For advanced Web users like me, the request part of the URL helps locate current page in the site, if there's a nice logic in the URL:
Safari unfortunately hides this request part, even on desktop:
For users with no technical knowledge about the URL structure, being able to detect fishing attempts immediately would be a huge security improvement:
That's why I really like what Jake suggests, as it makes the eTLD+1 obvious for security, but keeps the full URL alongside it, if there's enough space:
Optimising SVGs for the Web
The CSS Cascade, or how browsers resolve competing CSS styles
Last month I wrote some musings on default browser behaviours. When it comes to all the tasks that browsers do for us, the most fundamental is taking a URL, fetching its contents and giving us the results. As part of that process, browsers also show us the URL of the page currently loaded in a tab or window.
But even at this fundamental level, there are some differences from browser to browser.
Safari only shows you the domain name—and any subdomain names—by default. It looks like nice and tidy, but…