On Tue, Dec 22, 2015 at 12:04:29PM -0800, Kevin Carhart wrote: > We could keep this formulation in mind - it seems > like something I have stumbled on before: in the rendered > html, the user might hit something incongruous like > <Log in><Log out> > Combined with the fact that it doesn't work right. > One reason it could be this way is that site > authors have coded a > superset in their server-side code, and are intending > on using JS to always take away one of those on the > client side before it reaches the user. But then maybe > if the JS file breaks on something else (like Sibling > or other things), the JS file bails out and the code > responsible for the take-away is never reached. I > think maybe the candy-store website has this too.
I don't know about that specific website but yeah, I've seen this a lot. there are also sites and frameworks (names escape me right now) which use this kind of thing as a sort of app level cache mechanism by sending everything then deleting bits and dynamically filling in others with... you guessed it... AJAX. Cheers, Adam.
signature.asc
Description: PGP signature
_______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
