3 ms·
How would this handle accessibility? 64-128K page size is perfectly doable in HTML today if anybody actually cares enough to do it. How much of the bloat in s
by biztos 5y ago
How would this handle accessibility?
64-128K page size is perfectly doable in HTML today if anybody actually cares enough to do it. How much of the bloat in say an Amazon page is the JavaScript?
Is there something about your protocol that would prevent the big players from re-normalizing 1M page size with it?
- graiz 5y agoAccessibility is easier because items have clear locations and sizes without computing cascading rules. This also allows for easier navigation (left/right) in addition to traditional logical / tab-stop order. If done right it would be harder to screw-up. Current HTML is very easy to inadvertently hurt accessibility. In my tests it would be very difficult to create a 1Mb page. You would need 10,000 text/image/nodes of actual content (not tags or containers). This just doesn't happen. Presentation is strictly separated from code execution so first load is never blocked by code. Code can dynamically change the page but does so by directly changing the DOM using limited server side-commands. In other words it's truly a thin client browser. You can bloat up the server with as much code as you want but the client side stays lean.