microsoft / microsoft/vscode-edge-devtools

False positive: charset meta element warning despite correct placement in <head>

Open
#2,879 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug tracked
Dominant language
TypeScript
Stars
827
Forks
358
Avg merge
20h 32m
Merged PRs (30d)
10

Description

Environment (please complete the following information):

  • OS : Windows 11
  • Extension version : 2.1.8

Describe the bug:

Microsoft Edge Tools for VS Code incorrectly displays a warning that the charset meta element should be the first element in the head tag, even though it already is correctly positioned as the first element.

Repro steps:

  1. Open an HTML file in VS Code with Microsoft Edge Tools extension enabled
  2. Have a properly formatted HTML document with as the first element in the section
  3. Observe that the extension still shows a warning: "charset meta element should be the first thing in "

Image

Expected behavior:

No warning should be displayed when the charset meta element is already correctly positioned as the first element in the head tag.

Additional context:

The warning appears to be a false positive as the HTML already follows the recommended practice. The meta charset element is correctly placed as the first element in the head section, yet the linting still flags it as an issue. This creates confusion for developers who have already implemented the correct HTML structure.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the warning in a Windows 11 HTML file using Microsoft Edge Tools for VS Code 2.1.8, with as the first element in . Trace the charset diagnostic and verify that the warning disappears when the element is correctly placed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.