Microsoft Edge documentation

Microsoft Open Source Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct.
For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, navigate to the LICENSE file, and grant you a license to any code in the repository under the MIT License, navigate to the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
Microsoft general trademark guidelines may be found at https://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com.

Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

Contributing

This is the repository for Microsoft Edge documentation hosted at https://docs.microsoft.com/microsoft-edge/.

If you want to include new coverage or have feedback, consider contributing. You may edit the existing content, add new content, or create new issues. The Microsoft Edge team reviews a look at your suggestions and works to incorporate the suggestions into the docs.

Find the data for the Status page at: https://github.com/MicrosoftEdge/Status. The Status page provides the latest implementation status and future plans for web platform features in Microsoft Edge.

Conventions

• When adding a page, you must add an entry for it in toc.md for it to appear.
• A directory may contain more directories or readme.mds
• Folder/directory names are dash-separated (for example, f12-tools) and lowercase. Directories are used in URLs on the docs.microsoft.com site. Avoid using underscores, PascalCase, or camelCase.

Other text elements

These other text elements have styling available:

• Unordered lists
• Have regular bullets
  • You may also nest bullets.
  • Bullets lists should have more than one entry.
• Standard arrangement

1. Ordered lists.
2. Use regular western-style numbering.
3. Should be used only when a list truly has order.

---

Horizontal rules are available. Use horizontal rules sparingly to reduce clutter.
Avoid using horizontal rules with heading tags; some headings already use line styles for visual hierarchy.

Displaying code

You may use inline code Markdown syntax (with the backticks).

Or you may display blocks of code. The following code snippet is a css example.

body {
    background: #fff;
}

Tables

You may	use headers	on tables
Left-aligned	Unless a #	456
Text value	More text	$0.00

Notes

Use notes sparingly. The blocks are designed to highlight "don't-miss-it" information.

Four different versions of notes are currently styled.

• NOTE
• WARNING
• TIP
• IMPORTANT

Respectively, the notes look like the following code snippets.

> [!NOTE]
> This is a NOTE  

> [!WARNING]
> This is a WARNING  

> [!TIP]
> This is a TIP  

> [!IMPORTANT]
> This is IMPORTANT  

For multi-line blockquote notes, use a greater-than (>) character in front of each line of the notes as displayed in the following example.

> This is a line in a blockquote.  
> My text may wrap to more than one line when the Markdown is parsed, but I must include all my information within a single \(sometimes very long line\) in the Markdown.  
> This is another line in a blockquote.  

Images

Images should be stored in a media directory and referenced with a relative path using image script.

:::image type="complex" source="./media/notes.png" alt-text="Note patterns" lightbox="./media/notes.png":::
   Note patterns  
:::image-end:::