-
Notifications
You must be signed in to change notification settings - Fork 40.4k
[emmet] http-equiv="X-UA-Compatible" in 2023 #165933
Copy link
Copy link
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebtCode quality issuesCode quality issuesemmetEmmet related issuesEmmet related issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded
Milestone
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebtCode quality issuesCode quality issuesemmetEmmet related issuesEmmet related issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded
Type
Fields
Give feedbackNo fields configured for issues without a type.
The emmet expansions
!andhtml:5both produce this expansion:The
<meta http-equiv="X-UA-Compatible" content="IE=edge">meta tag is unnecessary and should be removed. It was last used in IE10 to turn on compatibility mode and now as even IE11 is dead, we can safely remove it.It was initially removed in 2019: #80923
Then added back in: #108119
Then suggested to remove it again in 2021, which Im pretty sure incorrectly says it was needed for ie11: #128374
Now that all IE is dead, let's get rid of it!