| 03:02 | <Domenic> | PSA for those who build the HTML Standard: Thanks to Jeremy Roman, whatwg/html-build has replaced its string-substitution Perl preprocessor code with proper-HTML-parsing Rust preprocessor code. Very cool! This opens up many future opportunities for improving the HTML build tooling as well. In case you don't want to install a Rust toolchain, you can also use the new If you run into any problems, please let me know or file an issue. |
| 08:07 | <i18u> | hi, does the spec have any word to describe about that, if a Data URL SVG image svg can have a use child element, in another word, if the DataURL svg image and the the target svg element share a same DOM scope? |
| 08:15 | <i18u> | for example: I have a SVG element contains some symbols. and have a img element use a DataURL, which use a SVG symbol of the main document. |
| 09:47 | <jason ji> | Hi, everyone. How can I know which new features(proposals) will be added to the HTML living standard? Which features will be implemented by browser vendors? Thank you in advance! |
| 09:53 | <jason ji> | ECMAScript has 5 stages for a new proposal, it's very clear. Does WHATWG have this kind of mechanism to let developers know which new features can be expected in the future? |
| 10:06 | <zcorpan> | jason ji: There's a proposal for such a mechanism, but it's optional to use. See https://github.com/whatwg/meta/issues/290 |
| 10:07 | <zcorpan> | jason ji: otherwise there's the "addition/proposal" label: https://github.com/whatwg/html/labels/addition%2Fproposal |
| 10:09 | <zcorpan> | jason ji: and you can track implementation status in blink-dev (chromium) or dev-platform (gecko), and the relevant bugs for each browser |
| 10:15 | <jason ji> | Thank you zcorpan , The solution I can think of is monitoring browser version releases. |
| 10:16 | <jason ji> | I will pay attention to those two proposals. |
| 10:17 | <zcorpan> | jason ji: yes, release notes tells you when it's shipping (maybe during beta). "Intent to prototype" emails tells you someone will start working on an implementation |
| 10:19 | <jason ji> | The current HTML standard can actually feel somewhat mysterious because there haven't been new versions or clear new feature releases. This can, in fact, diminish the standard's visibility among developers. |
| 12:40 | <annevk> | i18u: in theory that ought to work; at some point I added this local URL concept for it to Fetch, but SVG never properly integrated with it I think |
| 12:41 | <annevk> | i18u: https://fetch.spec.whatwg.org/#local-urls-only-flag |
| 13:46 | <annevk> | Alright, hopefully "directionality" and the dirname attribute are now in a state where they can remain unchanged for another decade or so, modulo the introduction of new text-based form controls |
| 14:40 | <aja> | curious how directionality is handled for lang=zxx |
| 14:41 | aja | has been using on lorem ipsum sorta things |
| 14:45 | <aja> | same on font samples. to avoid long bits of nonsense being read out by at |
| 14:45 | <annevk> | aja: it's not influenced by language at all |
| 14:49 | <Panos Astithas> | The next time they conflict seems to be Nov 30 |
| 16:14 | <zcorpan> | Panos Astithas: ok yeah, I guess I should clone myself :) |
| 17:14 | <Panos Astithas> | hehe |
| 21:28 | <el fenix King rv república de Venezuela> | Hila |