| 07:18 | <Domenic> | jsdom/whatwg-url, and thus Live URL viewer, has finally figured out its IDNA issues. Fun examples like https://jsdom.github.io/whatwg-url/#url=aHR0cHM6Ly94bi0tNC0wYmQxNTgwOGEuLi4v&base=YWJvdXQ6Ymxhbms= and https://jsdom.github.io/whatwg-url/#url=aHR0cDovL3huLS1sczhoPS8=&base=YWJvdXQ6Ymxhbms= now match the spec. |
| 08:46 | <zcorpan> | The spec PR preview links for html are in alphabetical order. Is it possible to make them be in the spec's natural order instead? |
| 08:47 | <zcorpan> | or maybe a link to an annotated ToC would be better |
| 14:20 | <annevk> | Domenic: oh that's great, good place to be in before Unicode considers our feedback |
| 19:48 | <Lucas Carlesso> | Is there a contradiction between the description of the b and strong elements? If strong can be used to "distinguish the part that really matters from other parts that might be more detailed, more jovial, or merely boilerplate." And "to denote the part of the text that the user is intended to read first." would not it also cover "key words in a document abstract" and "an article lede", which are given as use cases for the b element? |