| 00:46 | <sideshowbarker> | https://html.spec.whatwg.org/multipage/webappapis.html#incumbent:the-iframe-element
…amen to that |
| 07:27 | <zcorpan> | Curious that Element chooses the fingerprint image as the link card image |
| 08:20 | <Domenic> | We should likely just add some proper OpenGraph metadata... kitchen sink probably? |
| 08:59 | <annevk> | Isn't OpenGraph very much non-standard? |
| 09:01 | <annevk> | <meta property> doesn't exist. Probably something we'd have to admit defeat on, but that would be quite a bit of work. |
| 11:35 | <evilpie> | annevk: I just realized something with unknownMarkup that I had forgotten about. Unlike for elements, we don't know which attributes are known or unknown. |
| 11:42 | <annevk> | evilpie: that seems like something we can maintain; I also think that we should not have a global list for attributes that are essentially local to elements, we should flatten that (except for actual global attributes) |
| 11:44 | <evilpie> | I am not sure what you mean with flatten in that context. Do you mean have a list of attributes per element or not? { element-tag -> [attributes] } |
| 11:45 | <evilpie> | We talked about this a few times before, but at least for Gecko creating such a list is not straightforward |
| 11:47 | <annevk> | evilpie: yeah, similar to how elements works, embrace that in the default policy |
| 11:52 | <evilpie> | Just to clarify this, we would basically needs two maps { elements -> supported-attributes } and { elements -> baseline-allowed-attributes }, because otherwise we can't decide if "onclick" is a known not-allowed attribute, or an unknown attribute. |
| 11:53 | <evilpie> | we don't need this for elements, because we currently do this weird thing with basically checking for instanceof HTMLUnknownElement |
| 11:59 | <annevk> | Which is a bit of a hack... |
| 11:59 | <annevk> | And doesn't work for MathML or SVG I'd think. |
| 12:00 | <evilpie> | yes, I think we have for that https://github.com/WICG/sanitizer-api/issues/147 |
| 12:00 | <evilpie> | maintaining a list of supported elements is a lot easier still |
| 13:20 | <annevk> | evilpie: I think. that's why it's really important this becomes part of HTML, so that whenever we add an element or attribute, all the relevant lists get updated |
| 13:23 | <zcorpan> | HTMLUnknownElement check also doesn't work for custom elements |
| 14:23 | <Alex P> | Hey! Wombat is an awesome NFT gaming platform. Have you tried it? Download it now and earn a friendship NFT with me 😊 ! 1. Install the app via this link and finish the registration. 2. Complete the “claim referral rewards” quest in app Link: https://go.getwombat.io/puqN Code: KQ2KYZZ |
| 14:25 | <Ms2ger> | annevk: you around? ^ |
| 17:44 | <Dan> | Hi! Very cool that WHATWG is on Matrix! 🥳 I just submitted my very first proposal ever! 🙂 https://github.com/WICG/proposals/issues/125 |
| 17:52 | <Dan> | (Ofc. "Windows" is only an example, surely Linux distros also are affected by this or will be, in the future). I just made sure it says Windows as example. also just shortened the proposal, removed the "optional discussion" part in the end. |