| 01:00 | <crowlkats> | Whats the status of https://github.com/whatwg/streams/pull/1145? Deno is extremely interested in it |
| 01:00 | <Luca Casonato> | We're happy to do any necessary spec or integration work to get this landed. |
| 03:32 | <Domenic> | Waiting on implementer interest I believe. Might be similar to Response.json(), and a good candidate for https://github.com/whatwg/js-hosts/ while we wait. |
| 08:28 | <annevk> | It seems plinss turned it off and on again \o/ |
| 08:43 | <Andreu Botella> | For the record, I set up https://github.com/andreubotella/csswg-auto-build as an auto-building and auto-updating mirror for the CSS specs |
| 11:11 | <sideshowbarker> | For the record, I set up https://github.com/andreubotella/csswg-auto-build as an auto-building and auto-updating mirror for the CSS specs |
| 11:13 | <Andreu Botella> | I think bkardell shared it with Peter Linss |
| 12:33 | <stephanluis> | Inspired by a discussion on this chat, I've developed a time only input for use in HTML. Difference is that my input deals with time in HMSmS, which provides greater browser consistency. I want to confirm that all the functionality of the element as rendered by Chrome is included in my control, but cannot find a function spec. Does anyone on this board know where I might find it? |
| 12:47 | <annevk> | stephanluis: is https://html.spec.whatwg.org/ what you are looking for? (Though there is some stuff beyond that I suppose, such as supporting a variety of input methods, supporting multiple locales, etc.) |
| 13:15 | <stephanluis> | I've seen that thanks, I know it's now whatwg remit, but I'm hoping to be pointed in the right direction on how chrome or firefox implement the input. For example what the up and down arrow keys do when hours are selected. That way I can replicated the control more precisely. Now I think I have most of it, but would rather be more sure. Guessing their functional specs would be greatest help? |
| 13:26 | <annevk> | I see, I'm not sure if those exist or where to find them (other than looking at source code) |
| 14:05 | <stephanluis> | I even had a look at the source code but the documentation wasn't clear enough to use. Seemed like there is other documentation / specs to work from. Maybe I can try looking for Firefox specs, if their user interaction is close to chrome as people are most exposed to chrome. |
| 18:53 | <Timo Tijhof> | I could use a hand on proving/confirming that the behaviour I'm looking for from the URL constructor (in modern browsers, but not in the FT polyfill), is in fact a bug in the polyfill and not an spec bug or implemetnation bug. https://github.com/Financial-Times/polyfill-library/issues/4#issuecomment-1059423248 |
| 18:55 | <Timo Tijhof> | The URL version of this, is I think https://url.spec.whatwg.org/#percent-decode |
| 18:55 | <Timo Tijhof> | which seems almost too simple to be true |
| 18:55 | <Timo Tijhof> | compared to http://es5.github.io/#x15.1.3.2 and the whole Decode complexity and its URIError handling etc. |
| 19:07 | <TabAtkins> | Timo Tijhof: At a quick glance, it appears the ES algo might be implementing UTF-8 decoding by hand, thus the complexity. |
| 19:10 | <TabAtkins> | Andreu Botella: Btw, you can tell Bikeshed to output to any filename you want, so you don't have to do the rename to index.html manually. |
| 19:10 | <Andreu Botella> | oh, that's right |
| 19:11 | <Andreu Botella> | someone could try visiting the Overview.html directly, I guess |
| 19:11 | <Domenic> | I could use a hand on proving/confirming that the behaviour I'm looking for from the URL constructor (in modern browsers, but not in the FT polyfill), is in fact a bug in the polyfill and not an spec bug or implemetnation bug. https://github.com/Financial-Times/polyfill-library/issues/4#issuecomment-1059423248 |
| 20:28 | <Timo Tijhof> | Thanks, that helps. I've traced it down to https://github.com/jsdom/whatwg-url/blob/a4cb13309246ca9ecf03404fdbf0d23ecaf114dd/lib/urlencoded.js#L10-L33 and https://github.com/jsdom/whatwg-url/blob/a4cb13309246ca9ecf03404fdbf0d23ecaf114dd/lib/percent-encoding.js#L20 which indeed is doing the critically important thing of ignoring things outside the known valid range and leaving them in-tact, whereas the ES decodeURIComponent throws an error for anything unexpected after a % sign. |
| 20:28 | <Timo Tijhof> | I'll see if I can port that over to the FT polyfill in a somewhat standalone and minimal fashion. |
| 23:49 | <Domenic> | ๐ look at the list of issues fixed in https://github.com/whatwg/html/pull/6315#issue-790233208 |
| 23:58 | <Seirdy> | Besides search engines, what are some known working applications of microdata (and other related formats)? I've seen article extraction implementations (including DOM Distiller, Trafilatura) make use of it, for instance. |
| 23:58 | <sideshowbarker> | ๐ look at the list of issues fixed in https://github.com/whatwg/html/pull/6315#issue-790233208 Wild โ ~40 issues, looks like. I canโt recall ever having seen that the part of the GitHub UI that lists the linked issues shows a See more control when thereโs more than a certain number of linked issues โ 5, I guess โ but even if you do See more, it still limits the list to just 10 issues.
Bravo Jake Archibald |