fix: zensical strict mode fixes for comparison pages

[onuralpszr]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🛠️ This PR applies a large-scale docs consistency fix by HTML-escaping the active-models array in comparison page chart <canvas> tags across many model-vs-model pages.

📊 Key Changes

• Replaced raw JSON-like values such as ["YOLO11", "YOLO26"] with HTML-escaped equivalents like ["YOLO11", "YOLO26"] in the active-models attribute.
• Updated this pattern across a wide set of comparison docs in docs/en/compare/, including pages for DAMO-YOLO, EfficientDet, PP-YOLOE+, RTDETRv2, YOLO11, YOLO26, YOLOv10, YOLOv5, YOLOv6, YOLOv7, YOLOv8, YOLOv9, and YOLOX.
• No article content, benchmarks, or model recommendations were changed 📘
• The change is purely a markup/HTML-safety update focused on the embedded comparison chart configuration.

🎯 Purpose & Impact

• Improves HTML validity and reduces the chance that bracketed attribute values are misread by site generators, Markdown processors, or browsers ✅
• Helps keep interactive benchmark charts working reliably across many comparison pages 📈
• Lowers maintenance risk by standardizing how chart data is embedded in docs pages 🔧
• User-facing impact should be minimal visually, but readers may benefit from fewer rendering or parsing issues on comparison pages 🌐

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 30, 2026 5:16pm

[UltralyticsAssistant]

👋 Hello @onuralpszr, thank you for submitting this ultralytics/docs 🚀 PR! This is an automated message to help with review readiness—an engineer will assist you shortly. Please review the checklist below to help ensure a smooth merge ✨

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/docs main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

The PR looks clean based on the provided diff. The change is narrowly scoped, applied consistently across the comparison pages shown, and does not introduce any obvious functional, performance, or maintainability issues.

[onuralpszr]

Closed in favor of ultralytics/ultralytics#24389