4 ms·
No native font rendering True, but you can render some pretty good looking fonts[0]. no right-clicking text selection to choose from a dozen OS-provided se
by TheMakeA 13y ago
No native font rendering
True, but you can render some pretty good looking fonts[0].
no right-clicking text selection to choose from a dozen OS-provided services, no user-based keyboard shortcuts in text fields like this comment field, and so on.
Could be part of a JS api exposed and used by HTML5.js.
there wouldn't be a working DOM inspector in your browser
FireBug, and the Chrome Dev Tools are written in HTML. Could be integrated into HTML5.js.
There would be differences for sure, but I think the benefits would outweigh the downsides.
[0] http://research.microsoft.com/en-us/um/people/cloop/LoopBlinn05.pdf http://research.microsoft.com/en-us/um/people/cloop/LoopBlin...
- 0x0 13y agoThat's assuming everyone is on the official html5.js branch. Seems like it would be pretty easy for a million variants to be developed with all kinds of quick one-off hacks, that would make an off-the-shelf DOM inspector incompatible. It's like the ultimate "solution" to all those useless anti-view-source javascript efforts. (Imagine this taken to the extreme - encrypted home-grown markup and stylesheet languages that barely resembles html anymore.) Also, accessibility would take a major hit. Also, a huge amount of web sites will never update their html5.js. Sounds like the anti-web.