docs: remove redundant boolean attribute section

[ashutoshbisoyi]

1. Removed redundant boolean attribute sections in HTML coding standards
2. Merged the example to the existing section

Summary by CodeRabbit

• Documentation
  • Consolidated guidance on boolean attributes in HTML by removing a redundant section and enhancing examples in the remaining section for improved clarity.

[coderabbitai]

Walkthrough

The "Omit Boolean Attribute Value" section was removed from the HTML coding standards document. Its content was consolidated into the existing "Boolean Attributes" section, which was updated with additional examples to illustrate correct and incorrect usage of boolean attributes in HTML.

Changes

File(s)	Change Summary
coding-standards/html.md	Removed the "Omit Boolean Attribute Value" section and expanded the "Boolean Attributes" section with more examples.

Estimated code review effort

1 (~2 minutes)

Possibly related issues

• Proposal: Merge redundant boolean attribute sections in HTML coding standards #81: The changes directly implement the proposal to consolidate boolean attribute guidance and remove redundancy in the HTML coding standards.

Suggested labels

documentation

Poem

In the garden of code, where standards bloom bright,
A section removed, now the guidance is light.
Boolean attributes, concise and so neat,
One section to rule them, the guidance complete.
With clarity shining, our docs hop ahead—
A rabbit’s delight in the changes we’ve read! 🐇

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b65da15 and edea480.

📒 Files selected for processing (1)

• coding-standards/html.md (2 hunks)

[coderabbitai]

🛠️ Refactor suggestion

Include closing </audio> tag to stay aligned with the “Do Not Omit Closing Tags” rule

The examples add an <audio> element without its mandatory closing tag, which contradicts the guideline stated earlier in the same document (“Do Not Omit Closing Tags”, line 109).
Updating both “Bad” and “Good” snippets keeps the examples self-consistent and avoids signalling that <audio> is a void element (it is not).

-<audio autoplay="autoplay" src="/audio/theme.mp3">
+<audio autoplay="autoplay" src="/audio/theme.mp3"></audio>

…

-<audio autoplay src="/audio/theme.mp3">
+<audio autoplay src="/audio/theme.mp3"></audio>

Also applies to: 204-204

🤖 Prompt for AI Agents

In coding-standards/html.md at lines 194 and 204, the <audio> elements are
missing their mandatory closing </audio> tags, which violates the "Do Not Omit
Closing Tags" guideline. Add the closing </audio> tags to both the "Bad" and
"Good" example snippets at these lines to ensure consistency and correct HTML
syntax.

[ashutoshbisoyi]

@xixas perhaps we don't need to make this change. Let me know if this can be resolved without any changes

[coderabbitai]

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!