<textarea></aaaaa... should insert a text node?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- web-dev
Research direction
Start with the linked WHATWG issue comment and saved live DOM viewer examples 4224 and 4225, then compare the specification's tokenizer behavior with the browser behavior described here. Done means resolving the expected DOM and handling of the temporary buffer and documenting the agreed specification change or implementation requirement.
Written by the indexing model from the issue text.
Description
@RReverser found this in https://github.com/whatwg/html/issues/1257#issuecomment-220664626
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4224
window[0].document.write('<textarea></textar');
So far so good; no EOF yet (no document.close()) and a script might later write ea> to finish the end tag.
Now consider
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4225
window[0].document.write('<textarea></textart');
Per spec this should have the same DOM as the previous one, and the parser having consumed </textart into the temporary buffer, waiting for a > or space or slash or EOF.
Two problems:
- This can cause unnecessary OOM in streaming parsers that implement the spec literally, for
<textarea></aaaaaa... - Browsers disagree for this case; Gecko seems to check each character if it still matches what is expected, while WebKit/Blink/IE11 seem to fill the temporary buffer like the spec.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from whatwg/html
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
topic: media topic: rendering
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
clarification
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
compat topic: navigation topic: navigation API
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
tvOS
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bvaughn/react-resizable-panels#751 · 1 comment ·
-
www.wiwo.de OpenN: AdGuard Browser Extension P3: Medium T: Annoyance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
AdguardTeam/AdguardFilters#242026 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100