Description:
- follow-up to my previous PR #6060
(chore: MarkDown Note marker compatibility spacing)
Main directory: /browsers/
This is a follow-up attempt to standardize the MarkDown Note bubbles
by adding the recommended single space after the quote marker.
MarkDown codestyle & whitespace usage consistency is the main goal here.
Additional proposed changes:
- Remove redundant end-of-line (EOL) whitespace
- Simplify blank space usage in bullet point lists/numbered lists to 1
- Replace some tab characters with 4 blank spaces (GitHub compatibility)
- Reduce redundant blank line whitespace usage:
- remove excessive blank lines between sections
- remove surplus blank lines in minimal bullet point lists
File-specific improvement change:
browsers/edge/microsoft-edge-kiosk-mode-deploy.md
- Add back missing table readability spacing and cell dividers.
Ticket reference or closure:
None that I know of (at least not yet).
Additional notes:
- I have split this modification chore into sub-folder sections
to keep the number of files within a reasonably manageable amount.
- Some of the whitespace changes could not be applied due to layout.
Removing the sentence that has broken link - could not find a suitable replacement - checked with CSS SME from IE (Louis Shanks) and confirmed that we can remove the sentence with broken link.
Description:
This PR is a standalone attempt to standardize the MarkDown Note
bubbles by adding the recommended single space after the quote marker.
MarkDown codestyle consistency is the main goal here.
Changes proposed:
- Add single space between the quote marker and the text [!NOTE]
- Add the same spacing to the connected text line in the same bubble
- Apply the same standard to other nearby notes, e.g. [!IMPORTANT]
- Standardize on uppercase [!NOTE] instead of mixed casing ( [!Note] )
- Remove some of the obvious redundant spacing at end-of-file
Ticket reference or closure:
None that I know of (at least not yet).
Additional notes:
I have split this modification chore into sub-folder sections to keep
the number of files within a reasonably manageable amount.
Correcting the sample xml so that the comments don't break parsing rules. Also, updating the "Default" and "None" captialization to be consistent with our other documentation and tools.
Updating the "Deprecated attributes" section to be more accurate about elements and attributes. Also corrected samples.
This change fixes 2 issues in the "Schema Attributes" section.
1. This section uses < and > around the attribute names, which is confusing, because that is notation reserved for elements.
2. The description of exclude is a little vague and somewhat misleading.
The sample xml has a couple of problems that are fixed here.
1. Comments use -- not --- to begin and end. 3 hyphens will cause a parse error.
2. The default values for <compat-mode> (Default) and <open-in> (None) are not capitalized, which doesn't fit with other documentation and tools.
As previously discussed in this PR, I have converted the
**Important** section headings by using their MarkDown equivalent
> [!IMPORTANT] (as well as adding the blockquote for its text content).
- Resolve duplicate use of https where both http and https was intended
- MarkDown code fence XML tag corrections
- Replace HTML `<br>` codes with NewLine
- Remove redundant space at the end of the version 2 file
Resolves#4769
