4 ms·
Because most SPAs that I interact with (like ESPN) have no business being SPAs (in the sense of hijacking navigation). The main motivation behind constructing t
by caditinpiscinam 3y ago
Because most SPAs that I interact with (like ESPN) have no business being SPAs (in the sense of hijacking navigation). The main motivation behind constructing them that way seems to be to circumvent UX safeguards.
- pier25 3y agoWouldn't it make more sense to just stop using apps like ESPN instead of breaking a major browser API and big chunk of the internet?
- skydhash 3y agoWould you stop using GitHub as well. They recently move to a SPA models and I think search and readme links were broken for a few days because of history hijacking.
- pier25 3y agoI wouldn't but my point is that a) no one is forcing anyone to use a website and b) it seems absurd to break a major browser API.
- caditinpiscinam 3y agoThe key to what I'm envisioning is that it wouldn't break a site like ESPN entirely -- it would just break the SPA behavior by making links behave like links. The end result is that the site would be more usable, not less. For sites where SPA behavior is necessary (like Spotify), opting in could be done with a one-time browser prompt, like how location access and DRM playback are handled. This seems like a more realistic solution than just avoiding these sites altogether, for the same reason that people use ad blockers instead of just shunning sites with ads.
- pier25 3y ago> This seems like a more realistic solution It's completely unrealistic to break a major browser API.
- caditinpiscinam 3y agoHow many web apps from 15 years ago still work? Flash, Java applets, browser specific hacks, fingerprinting, cross-origin shenanigans... all locked down or eliminated. The internet evolves by breaking APIs.