Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove BestStandardsSupport middleware
- Loading branch information
1 parent
88e4ec6
commit 3bccd12
Showing
9 changed files
with
3 additions
and
108 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
30 changes: 0 additions & 30 deletions
30
actionpack/lib/action_dispatch/middleware/best_standards_support.rb
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
30 changes: 0 additions & 30 deletions
30
railties/test/application/middleware/best_practices_test.rb
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎 Without this, the UI for switching to a non-standards compatibility mode is still provided, and I have encountered users who got into a bad mode accidentally, breaking the site, and didn't know how to fix it.
3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can set this header manually.
3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfirebaugh this wasn't completely removed, was just moved to the set of default headers (
config.action_dispatch.default_headers
) since we don't want to have a middleware just to add a header.3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the pointer. The default
default_headers
results inX-UA-Compatible: chrome=1
. I would say it should beX-UA-Compatible: IE=Edge,chrome=1
, to match Rails 3 behavior and eliminate the possibility of the user accidentally switching to a non-standards compatibility mode.3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfirebaugh unfortunately we can't change it again now or it will break people application that expect only
chrome=1
3bccd12
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's worth noting that because of the removal of
IE=Edge
certain users may now be served pages in compatibility mode because of their intranet settings. In our case it renders pages in IE7 compatibility mode. The only way to work-around these intranet enforcements is by explicitly addingIE=Edge
back.