fix(plugin): sanitize markdown and prevent horizontal overflow

[bajrangCoder]

• Remove <style> tags from plugin markdown via DOMPurify FORBID_TAGS
• Prevent horizontal overflow in markdown content sections
• Improve table styling with proper borders, padding, and hover effects
• Improve hr styling to use theme-consistent border color
• Add word-break and overflow-wrap for long content
• Make tables and images responsive with max-width constraints

[gemini-code-assist]

Summary of Changes

Hello @bajrangCoder, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the display and security of markdown content within the plugin. It introduces robust sanitization to prevent malicious style injections, improves content readability by preventing horizontal overflow and ensuring responsiveness for images and tables, and refines the visual presentation of tables and horizontal rules for a more consistent and user-friendly experience.

Highlights

• Markdown Sanitization: The plugin's markdown content now explicitly forbids <style> tags during sanitization using DOMPurify, enhancing security by preventing potential style injection.
• Horizontal Overflow Prevention: Markdown content sections are updated to prevent horizontal overflow, ensuring long words break correctly and making images and tables responsive within their containers.
• Improved Table Styling: Tables within markdown content have received significant styling enhancements, including proper borders, padding, zebra-striping for rows, and hover effects for better readability and user experience.
• Consistent HR Styling: Horizontal rules (<hr>) are now styled to use a theme-consistent border color, improving visual coherence across the application.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces several good improvements for rendering markdown content. It enhances security by sanitizing <style> tags, and improves the layout by preventing horizontal overflow and making elements like images and tables responsive. The styling for tables and horizontal rules is also much improved and consistent with the theme.

My review includes a few suggestions for the SCSS changes to improve maintainability by removing redundant properties and avoiding overly broad CSS selectors. Overall, this is a solid set of changes.