New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Window load example regression #10771
Comments
same example is affecting on following event pages |
@wbamberg I suggest moving this over to yari, unless you would like to keep it here? |
I didn't move this to Yari so we can track it here if we want to work around it in content. So I think whether to move it to Yari depends on how likely it is to get fixed in Yari, or whether content should work around it. Which also I guess depends on what the "contract" offered by the live sample system to content authors is. With so many live samples on MDN and so many subtleties around the system, it feels like a spec is needed if we are to avoid errors/regressions. |
@wbamberg Works for me. Please open a new issue for the problem you're experiencing. |
For this example: https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event#live_example ...in the output I see this: ...in the pre-Playground version (https://web.archive.org/web/20230322100016/https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event#live_example) I see this: |
The page for https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event has an example showing the order in which
load
andDOMContentLoaded
events are fired. As recently as June 13, 2023 this example worked, but since the new live sample system launched it has stopped working.Perhaps this is because in the new system
DOMContentLoaded
fires before the script runs.The text was updated successfully, but these errors were encountered: