DOMContentLoaded does not fire in LiveSample

[debiru]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Document/readystatechange_event

What specific section or headline is this issue about?

The play function

What information was incorrect, unhelpful, or incomplete?

https://developer.mozilla.org/en-US/docs/web/api/document/readystatechange_event#result says "load" only.

What did you expect to see?

The result says:

DOMContentLoaded
readystate: complete
load

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

I think this issue should be addressed in the yari repository. Sorry if this has already been reported.

MDN metadata

Page report details

• Folder: en-us/web/api/document/readystatechange_event
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/Document/readystatechange_event
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/document/readystatechange_event/index.md
• Last commit: mdn/content@41a8b9c
• Document last modified: 2023-04-07T05:52:28.000Z

[Kaiido]

The same code sample can also be seen in https://pr31723.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/Document/DOMContentLoaded_event, and https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event.
https://developer.mozilla.org/en-US/docs/Web/API/touch_events, and https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Building_blocks/Looping_code are also affected (mdn/content#31288 is caused by this).
The issue seems to be that the JS content is actually inserted after the page load, and while a synthetic load event is manually fired, there is nothing for the other events that should have fired too, and all the properties that should denote a loading document in general will be wrong.

While mdn/content#31288 could be fixed easily by not waiting for that event anymore, it seems indeed problematic that the feature as a whole can't handle these cases properly.

[bsmth]

Thanks a lot to both of you for reporting and investigating 🙏🏻 I've moved this over to Yari which I think is the right place for it!

[wbamberg]

@caugner, this does not seem to be fixed by #10770 .

[Kaiido]

@caugner the initial report links to a section that still reproduces the original issue. Your playground isn't listening for the event in the same way.
To fix it and other related issues, you'd need to fire the DOMContentLoaded event from the document (and to make it bubble) and to also fire a readystate event.

This issue has not been fixed yet.