| 02:55 | <Max> | Does anyone know if there's a way to get the original/real dimensions of an image on an Image/<img> before the browser does its 'intervention' - ie the image in the file that is served by the web server? |
| 02:59 | <sideshowbarker> | Max: https://html.spec.whatwg.org/multipage/embedded-content.html#dom-img-naturalwidth maybe |
| 03:02 | <sideshowbarker> | or https://html.spec.whatwg.org/multipage/embedded-content.html#dom-img-naturalwidth-dev is a better link I guess (so-called “domintro”, specifically for developers) |
| 03:02 | <sideshowbarker> | or maybe even better, https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/naturalWidth and https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/naturalHeight |
| 07:31 | <foolip> | https://browser.engineering/ looks cool. |
| 08:34 | <sideshowbarker> | https://browser.engineering/ looks cool. |
| 08:37 | <sideshowbarker> | Needing to escape the HTML markup of every HTML example you want to put into a book about the web would seem to make HTML a bad choice for as the source for a book about creating or processing content for the web… |
| 08:38 | <sideshowbarker> | Not sure how many people know yet that the plan for MDN is to move all the MDN sources to markdown |
| 08:39 | <sideshowbarker> | It would be nice if one day most specs are written in markdown rather than HTML |
| 08:42 | <sideshowbarker> | I thought Bikeshed already fully supported writing spec source fully in markdown — but I can’t say I’ve seen any specs yet that are fully written in markdown (including any CSS specs) |
| 08:43 | <sideshowbarker> | specs with Bikeshed sources seem to all still have h1-h6 and <p> etc. |
| 08:44 | <Ms2ger> | I don't use <p>, but if you're going to add an ID anyway, there's not much of a win in using markdown for headers |
| 08:44 | <sideshowbarker> | ah yeah that makes sense |
| 08:45 | <Ms2ger> | Also not sure how to do <div algorithm> and <dfn> in md |
| 08:46 | <sideshowbarker> | luckily, for MDN we don’t have need for <div algorithm>, and not much need for <dfn> |
| 08:47 | <foolip> | I honestly can't get myself very excited about Markdown over HTML, there's a lot of things to remember and gotchas either way. But I'm happy to go along with it since other people seem to like it :) |
| 08:47 | <sideshowbarker> | well, to me, the biggest win for MDN is not needing to escape code examples |
| 08:48 | <sideshowbarker> | it’s just very ugly and very error-prone |
| 08:48 | <foolip> | Yeah, that's nice, I guess it will use ``` instead? |
| 08:49 | <sideshowbarker> | right |
| 08:49 | <sideshowbarker> | and automatically get syntax highlighting |
| 08:50 | <sideshowbarker> | hmm, well, while I think of it, another huge win is that I’m no longer forced by style policy to use <strong> and <em> instead of just <b> and <i> |
| 08:51 | <jgraham> | markdown is at least better than the weird HTML-but-not thing that the HTML spec uses |
| 08:52 | <sideshowbarker> | well, bikeshed specs arguably use even more weirdly HTML-but-not syntax |
| 08:53 | <jgraham> | Particuarly the mix of "we just invented the <ref> element" and "internal links are now written as <span data-x=target> because x isn't a real attribute" |
| 08:54 | <sideshowbarker> | ah yeah that stuff is ugly |
| 08:57 | <sideshowbarker> | another thing we’ve been doing for the MDN sources in preparation for moving to markdown is, trying to figure out if/how to replace background colors in tables with something that achieves the same effect |
| 08:58 | <sideshowbarker> | an example of something that got changed for that reason is the Sameness Comparisons table at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Equality_comparisons_and_sameness#a_model_for_understanding_equality_comparisons |
| 08:59 | <sideshowbarker> | previously the cells there had either green or red backgrounds |
| 08:59 | <sideshowbarker> | but those background colors got replaced with ✅ U+2705 WHITE HEAVY CHECK MARK and ❌ U+274C CROSS MARK emoji |
| 09:00 | <sideshowbarker> | I claim it’s actually an improvement — but I can imagine others might not agree |
| 12:53 | <Piers Wombwell> | Just spotted https://html.spec.whatwg.org still says "Join us on IRC, #whatwg on Freenode", which links to https://wiki.whatwg.org/wiki/IRC which redirects to https://whatwg.org/irc, but both should probably redirect to https://whatwg.org/chat and the spec page also just link to /chat and say 'Chat with us, Matrix or IRC', or similar. Not exactly urgent :-) |
| 12:54 | <Piers Wombwell> | Well, that's more verbose than I'd expected. |
| 12:58 | <jgraham> | Good catch |
| 13:32 | <Luca Casonato> | Where are the constructor steps for "Event" defined in the HTML spec? Can't find them anywhere in https://dom.spec.whatwg.org/#interface-event. Specifically looking for the initialization steps for timeStamp. |
| 13:34 | <foolip> | https://dom.spec.whatwg.org/#constructing-events says a lot of stuff |
| 13:35 | <foolip> | I think it’s like this to deal with init dicts in a single place |
| 13:37 | <Luca Casonato> | Ah... thanks :-) |
| 14:17 | <EveryOS> | Only a thousand lines? My RE is many thousand lines and I've still not gotten even close to JS. Surely that book must be using tons of premade libraries. |
| 14:29 | <EveryOS> | Ah, I see, it's just a super tiny subset |
| 14:55 | <wanderview> |
|
| 14:59 | <EveryOS> | First, its impressive whenever an external person shows up with a CL in crbug. Second, its extra impressive for someone to take a vague 1-line problem statement and turn it into a complete working solution. So well done! (And I work at google and often can't get UX feedback because they are so busy, so extra well done for engaging so well with them!) |
| 17:43 | <zcorpan> | welcome Rick Byers |
| 17:44 | <Rick Byers> | Hey zcorpan , good to see you! |
| 17:44 | <Rick Byers> | foolip just told me I needed to learn to use Matrix, so I'm trying :-) |
| 17:45 | <zcorpan> | I guess many of us are matrix noobs here |
| 23:23 | <devsnek> | in this modern era, is there a way to display an svg without opening yourself up to arbitrary js |