| 13:34 | <holst> | I was reading on W3Schools.com that for HTML5 "UTF-8 is the default"; I also saw in the https://encoding.spec.whatwg.org/#encodings site that all non-unicode encodings are "legacy". How should I interpret W3Schools.com - Are they simply wrong? |
| 13:35 | <holst> | or is UTF-8 the "default" in the sense that it is strongly recommended? |
| 13:46 | <holst> | https://www.w3schools.com/tags/ref_charactersets.asp |
| 14:07 | <andreubotella> | holst: due to backwards compatibility issues, websites without a meta charset tag can' |
| 14:08 | <andreubotella> | can't be interpreted as UTF-8 |
| 14:08 | <andreubotella> | but it very much is the default in the sense that the overwhelming majority of new sites use it |
| 14:28 | <andreubotella> | that link from w3schools with a mapping across the "character sets" is confusing and wrong, though |
| 20:11 | <domfarolino> | What in the spec corresponds to the user directly typing in a new URL in the URL bar to navigate to? Just the #navigate algorithm where the resource is the URL? It doesn't seem like any other algorithms capture this process earlier, but I wanted to ask around |
| 20:18 | <domfarolino> | I guess we'd need something to define that we reuse the existing browsing context though. This would seemingly go through "The rules for choosing a browsing context" and land in the "If the user agent has been configured such that in this instance it will reuse current", but nothing seems to specify that we invoke the "rules for choosing ..." algorithm in the scenario I describe |
| 21:07 | <Domenic> | domfarolino: not really specified, indeed. https://github.com/whatwg/html/issues/5381 |
| 21:08 | <Domenic> | All we've got is "A user agent may provide various ways for the user to explicitly cause a browsing context to navigate, in addition to those defined in this specification." |
| 21:12 | <domfarolino> | Domenic: Hah, I saw that too. Ok got it |