Open
Should the “DOM clobbering” note mention the id attribute as well?
clarificationgood first issue
5 comments0 reactions0 assignees
Issues
Open
"determine the value of a named property" should not imply a new object each time
good first issueneeds teststopic: forms
11 comments0 reactions0 assignees
Open
Investigation requested for beforeprint/afterprint
clarificationgood first issueneeds tests
4 comments0 reactions0 assignees
Open
Immediate token handling and "next token" are incompatible
clarificationgood first issuetopic: parser
9 comments0 reactions0 assignees
Open
Update all "queue a task" invocations to explicitly specify their task source
clarificationgood first issuetopic: event loop
3 comments1 reaction0 assignees
Open
The "rules for updating the text track rendering" are not run when mode changes from hidden to showing
good first issuetopic: media
4 comments0 reactions0 assignees
Open
Unclear if error event from "update the image data" matches implementations
good first issuetopic: img
4 comments0 reactions0 assignees
Open
Escaped characters in source
good first issue
4 comments0 reactions0 assignees
Open
createImageBitmap's note is wrong
good first issuetopic: canvas
4 comments0 reactions0 assignees
Open
Small clarity improvements to canvas transform methods
clarificationgood first issuetopic: canvas
7 comments1 reaction0 assignees
Open
About the term "top-level-browsing-context"
clarificationgood first issue
5 comments0 reactions0 assignees
Open
More infinite/NaN handling for <canvas> API members
good first issueneeds teststopic: canvas
2 comments0 reactions0 assignees
Open
Define `<input capture>`, ideally with a hint for which camera to use
good first issueintegrationtopic: forms
14 comments0 reactions0 assignees
Open
onerror and onunhandledrejection/onrejectionhandled could use some nice developer-friendly examples
clarificationgood first issuetopic: error reporting
2 comments0 reactions0 assignees