01:47 | <joshua.shaw> | Hello guys !!!!! ,…….WE POST ALL PRODUCTS AND REVIEWS ON OUR MAIN CHANNEL AND GROUP. WE WON'T BE POSTING ANY PRODUCTS ON THIS CHANNEL.MAIN GROUP AND CHANNEL LINKS BELOW ⬇⬇⬇ SUBSCRIBE HERE CHANNEL : https://t.me/+ioqje81ziAYyYTc0 https://t.me/+ioqje81ziAYyYTc0 https://t.me/+ioqje81ziAYyYTc0 https://t.me/+ioqje81ziAYyYTc0 https://t.me/+ioqje81ziAYyYTc0
3)✅Cashapp 4)✅Apple Pay 5)✅ PayPal 6)✅Venmo 7)✅Test run 8)✅Linkable 9)✅CC’s drop JOIN OUR MAIN TELEGRAM CHANNEL NOW |
07:54 | <Domenic> | (For the record, Anne answered Tab's question at https://github.com/w3c/csswg-drafts/issues/11005#issuecomment-2394293590 ) |
16:46 | <annevk> | It wasn't discussed in WHATNOT. It was discussed in this channel, but only two messages or so. |
20:38 | <Jay Madden> | Hello, I am working on fixing some wpt tests for ladybird and am working on the following suite http://wpt.live/html/semantics/interactive-elements/the-details-element/toggleEvent.html I have run into an issue on the last test however. For the following code
Chrome will send the event even tho. from reading the spec on navigables that document should never be marked as true https://html.spec.whatwg.org/multipage/document-sequences.html#node-navigable Which means the tasks from that DOM should never be runnable right? https://html.spec.whatwg.org/#concept-task-runnable So basically my question is, why do documents parsed with DOMParser() trigger events? |