Skip to content

http-equiv="X-UA-Compatible" in 2018 #58796

@ghost

Description

Do we still need

<meta http-equiv="X-UA-Compatible" content="ie=edge">

that ships with Emmet => ! tab ?

Metadata

Metadata

Assignees

Labels

emmetEmmet related issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions