Skip to content

Fix unrendered mx-imgBorder div#14382

Open
kinu404 wants to merge 1 commit into
MicrosoftDocs:mainfrom
kinu404:patch-2
Open

Fix unrendered mx-imgBorder div#14382
kinu404 wants to merge 1 commit into
MicrosoftDocs:mainfrom
kinu404:patch-2

Conversation

@kinu404

@kinu404 kinu404 commented Jul 2, 2026

Copy link
Copy Markdown

Fixes the [!div class="mx-imgBorder"] markup leaking into the rendered page in the "Enable or disable inheritance for a specific repository" section of Set Git repository permissions.

Problem: The [!div] extension and its image were missing the blockquote (>) prefix, so DocFX didn't parse them as an extension and rendered [!div class="mx-imgBorder"] as literal text next to the screenshot.

Fix: Added the > prefix to both the [!div] line and the image line so they form a single blockquote, matching the correctly rendered usage in the "Set permissions for a specific user" section of the same file.

Fixes the `[!div class="mx-imgBorder"]` markup leaking into the rendered page in the "Enable or disable inheritance for a specific repository" section of Set Git repository permissions.

Problem: The `[!div]` extension and its image were missing the blockquote (`>`) prefix, so DocFX didn't parse them as an extension and rendered `[!div class="mx-imgBorder"]` as literal text above the screenshot.

Fix: Added the `>` prefix to both the `[!div]` line and the image line so they form a single blockquote, matching the correctly rendered usage in the "Set permissions for a specific user" section of the same file.
@prmerger-automator

Copy link
Copy Markdown
Contributor

@kinu404 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

1 similar comment
@prmerger-automator

Copy link
Copy Markdown
Contributor

@kinu404 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-regandowner

Copy link
Copy Markdown
Contributor

@Battle-born

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants