News for hackers. Stuff that matters.
Re:Escaping the SPA rabbit hole with modern Rails by acdha on Sunday July 08, 2018 @09:42AM (#17483747)
It is an issue with SPAs as a concept because part of that concept is that you’re taking on responsibility for things the browser traditionally did for you.

That’s not a bad thing but it’s extra work which someone has to be responsible for, similar to how e.g. using a complex custom widget means you’re on the hook for accessibility rather than the browser vendors.

Re:Escaping the SPA rabbit hole with modern Rails by baddox on Sunday July 08, 2018 @06:31PM (#17486640)
Surely most creators of SPAs are using some routing library, and I’m not aware of any routing libraries that don’t handle this anchor tag click behavior by default. It’s really a trivial amount of “responsibility” to take on.
Re:Escaping the SPA rabbit hole with modern Rails by acdha on Sunday July 08, 2018 @11:19PM (#17487745)
Perhaps, but it’s something I encounter fairly regularly, especially when an unreliable network connection or other JavaScript failure breaks something with poor error handling. Again, not a showstopper but it’s a decision point: if you aren’t committed to testing this kind of thing on every release, you don’t have the resources to build an SPA.
Re:Escaping the SPA rabbit hole with modern Rails by emodendroket on Monday July 09, 2018 @10:13AM (#17490283)
It's no different than stuff like not trusting browser input or avoiding a massive session when you're working on a Web app: it's simply basic best practice stuff that you don't even have to think about if you have an idea what you're doing.