infix form missing for `||` operator in Figures 26, 27
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 56
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Disclaimer: I might be misunderstanding the dictionary lookup!
The operator || (two ASCII characters) has infix, prefix, and postfix forms listed in Figure 29. However, the lookup algorithm in B1 remaps || to 0x0331, which only has prefix and postfix forms in Figures 26, 27.
Since the algorithm in 3.2.4.2 says you should try infix, postfix, prefix until you find a non-default answer, || never gets the infix spacing.
In fact, Google Chrome 135 seemingly adds no space around infix instances of ||.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by comparing the || entries in Figures 26, 27, and 29 with the lookup algorithm in B1 and section 3.2.4.2. Confirm whether the remapping to 0x0331 suppresses the infix form, then update the relevant specification text or tables so the intended infix spacing is selected and verify the algorithm remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100