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

1. ( GBP DOLLARS, EURO), PROP NOTES, WHITE CARDS, PAYPAL TRANSFER

2. ✅Cloned Card

3)✅Cashapp

4)✅Apple Pay

5)✅ PayPal

6)✅Venmo

7)✅Test run

8)✅Linkable 

9)✅CC’s drop 

JOIN OUR MAIN TELEGRAM CHANNEL NOW

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

<input id="clickMe" type="button" value="clickme" onclick="doFunction();" />
<script>
function doFunction() {
    new DOMParser().parseFromString("<h1><details open></h1>", "text/html").querySelector("details").ontoggle = function(e) {
      console.log(e.target.open);
    };
}
</script>

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?