Add dynamic browser compatibility badges

[grosmar]

Summary

Added dynamic browser compatibility badges from Browser Calendar (browsercalendar.com) to the Web Browsers section.

These badges verify browser version compatibility in real-time and support semantic versioning operators.

What's added

• Chrome, Firefox, Edge, and Safari compatibility badges
• Multi-browser combined badge example
• Documentation for supported operators (<=, <, >=, >, ^, ~, =)
• Usage examples and link to the badge generator

Why this is useful

Unlike static badges, these dynamically check if a specified version requirement is met against current browser releases. Useful for projects that need to document browser support requirements in their README.

Summary by CodeRabbit

• Documentation
  • Added browser compatibility badges to the project docs: individual badges for Chrome, Firefox, Edge and Safari.
  • Added a consolidated multi-browser compatibility badge combining Chrome, Firefox and Edge.
  • Documentation-only update; no code, API, or runtime changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Inserted browser compatibility badges into README.md's Web Browsers section: per-browser badges for Chrome, Firefox, Edge, Safari and a multi-browser composite badge; changes are documentation-only, no code or public API modifications. (42 words)

Changes

Cohort / File(s)	Summary
Documentation README.md	Added browser compatibility badges: individual badges for Chrome, Firefox, Edge, Safari (with version constraints and URLs) and a consolidated multi-browser compatibility badge; purely README content updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 I bound through README fields of light,
Badges gleam like stars at night,
Versions whispered, tiny and bright,
A hop, a note — docs set right,
— from a rabbit full of delight ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding dynamic browser compatibility badges to the README, which aligns with the changeset's addition of browser badges.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c521c8 and 072556b.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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 b5d6e37 and 3f8c386.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

README.md

1036-1036: Images should have alternate text (alt text)

(MD045, no-alt-text)

---

1037-1037: Images should have alternate text (alt text)

(MD045, no-alt-text)

---

1038-1038: Images should have alternate text (alt text)

(MD045, no-alt-text)

---

1039-1039: Images should have alternate text (alt text)

(MD045, no-alt-text)

---

1040-1040: Images should have alternate text (alt text)

(MD045, no-alt-text)

🔇 Additional comments (1)

README.md (1)

1030-1049: Well-organized new browser compatibility badges section.

The new "Dynamic Browser Compatibility Badges" section is clearly structured with good documentation, practical examples, and a link to learn more. The supported operators list (line 1042) and usage examples (lines 1044-1047) effectively communicate how to use the badges.

Please verify that the browsercalendar.com API endpoints referenced are stable and reliable for production use. If this service is subject to outages or version changes, you may want to consider adding a note about fallback options or alternative approaches.