4 ms·

i'm interested in the answer to this question as well and did a bunch of searching a while back to no avail. maybe the world is waiting for us to start?

YoshiRulz 3y ago
The tag is `<!DOCTYPE html>` and it should be the first line in the file/stream. Doing anything else will enable "quirks mode"[1]. Beyond that, the best thing you can do is avoid features that haven't been standardised yet or that were only standardised recently. [1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode#how_do_browsers_determine_which_mode_to_use https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mod...
eitland 3y ago
I have absolutely no idea about html rendering so my only contributions so far has been to ask/suggest to people who could know. But it is an idea that I keep getting reminded about. It could work adoption wise, since if it can be done technically it can be adapted independently of everyone else on backend and frontend: - backwards compatible, if a browser doesn't take advantage of it it renders completely ordinary and in supporting browsers if a website doesn't use this trick it just renders as any other website - If just one browser and one website does implement this then there will be a full setup. If the idea worked and for example Firefox supported this and Wikipedia or someone else took advantage of it suddenly everyone who used Wikipedia would se faster load and less battery usage.
- khimaros 3y ago
  my assumption is that this would be a strict subset of existing HTML/CSS/JS so that existing browsers would work without modification. but a small enough subset that hobbyist browsers could realistically implement the entire standard. it may make sense to look at browsers such as elinks and dillo for defining that subset.

4 ms·

i'm interested in the answer to this question as well and did a bunch of searching a while back to no avail. maybe the world is waiting for us to start?

by khimaros 3y ago

YoshiRulz 3y ago
The tag is `<!DOCTYPE html>` and it should be the first line in the file/stream. Doing anything else will enable "quirks mode"[1]. Beyond that, the best thing you can do is avoid features that haven't been standardised yet or that were only standardised recently. [1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode#how_do_browsers_determine_which_mode_to_use https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mod...
eitland 3y ago
I have absolutely no idea about html rendering so my only contributions so far has been to ask/suggest to people who could know. But it is an idea that I keep getting reminded about. It could work adoption wise, since if it can be done technically it can be adapted independently of everyone else on backend and frontend: - backwards compatible, if a browser doesn't take advantage of it it renders completely ordinary and in supporting browsers if a website doesn't use this trick it just renders as any other website - If just one browser and one website does implement this then there will be a full setup. If the idea worked and for example Firefox supported this and Wikipedia or someone else took advantage of it suddenly everyone who used Wikipedia would se faster load and less battery usage.
- khimaros 3y ago
  my assumption is that this would be a strict subset of existing HTML/CSS/JS so that existing browsers would work without modification. but a small enough subset that hobbyist browsers could realistically implement the entire standard. it may make sense to look at browsers such as elinks and dillo for defining that subset.