Skip to content

[emmet] http-equiv="X-UA-Compatible" in 2019 #80923

@p0358

Description

@p0358

html:5 macro still includes <meta http-equiv="X-UA-Compatible" content="ie=edge">
According to all the sources, it should be definitely unneeded nowadays.
This has been previously reported in #58796, where issue was locked and limited to collaborators. It was marked as upstream and suggested opening an issue at emmetio/expand-abbreviation (now archived). However emmetio/expand-abbreviation#28 shows that is has already been disabled there.
Why is it still kept in VSCode?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue identified by VS Code Team member as probable bugemmetEmmet related issues

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions