Browsers are pretty good at loading pages
carter.sande.duodecima.technology
Browsers are pretty good at loading pages
1–10 of 328 posts
Re: Browsers are pretty good at loading pages
#2Re: Browsers are pretty good at loading pages
#3The only thing worse is a custom scroll UI.
Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at it?
It's infuriating.
Re: Browsers are pretty good at loading pages
#4I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position. The only thing worse is a custom scroll UI. Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at…
Re: Browsers are pretty good at loading pages
#5I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position. The only thing worse is a custom scroll UI. Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at…
Slow? I'm quite sure the whole point of client side apps is for them to be substantially faster - and most are.
Re: Browsers are pretty good at loading pages
#6Re: Browsers are pretty good at loading pages
#7Re: Browsers are pretty good at loading pages
#8Re: Browsers are pretty good at loading pages
#9Re: Browsers are pretty good at loading pages
#10I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position. The only thing worse is a custom scroll UI. Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at…
More often than not, I've seen that tracking scripts break this more than anything else. Particularly command+click.
Still - it'd be great of there was an API to preserve UI state moving into a new entry in browser history. I don't want to lose scroll position for a sidebar if I'm drilling down into a large list of data.
Being able to add hints through markup for when to preserve UI state could go a long way towards making page-refresh based form and navigation behavior competitive again.