13 comments

[ 2.2 ms ] story [ 41.7 ms ] thread
Would an SPA be considered hijacking the fundamental nature of what the web was intended to be?
No
Just odd that HTML documents were basically the web for decades then SPAs came about and people quit using them.

SPAs are inherently difficult to SEO, difficult to parse by a third party, create their own DOM, etc.

It seems like instead of working to make the browsers do what people wanted they just did it with Javascript.

This is flamebait.
Yeah, I expect my browser to go backwards when I click back to another site, not be directed to another page on that domain. Also Pinterest hijacks the share function finch of Chrome on Android and will share a link to a main page of sorts.
Pinterest is web cancer. They steal pictures from other sites and then don't let you get back to the source.
(comment deleted)
See also: sites that bind the forward-slash (/) key to their own search box instead of letting it fall through to the standard browser Find In Page behavior.
Also the standard CTRL+L/CMD+K to get to the browser's search engine box. Browsers really should have a list of shortcuts that they just never allow to fall through to the page context.
Github does this. It makes me angry.
I just had to reinstall Firefox Mobile (clearing all settings) and then I wasn't able to zoom on a lot of websites. Fortunately FF has an option for that but I wonder why there needs to be such an option. Why would a website-maker decide it's better when I'm not able to zoom on their website and why can they do that at all?
Making the browser behavior accessible to web sites is a design error.
The committer is confusing two different things here.

If you edit your browser setting regarding smooth scrolling you set what happens when you scroll on your input device, i.e. touchpad, mouse wheel or whatever.

If you as a website developer set the `scroll-behaviour` css property you control what happens when the browser changes scroll position for ex. if you programatically change the focus.