docs: fix case-sensitivity explanation in highest-available-document-mode #6029
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull request checklist
Make sure you:
For non-trivial changes, please make sure you also:
Short description of the change(s)
This PR improves the behavior of the highest-available-document-mode hint by fixing an incorrect case-sensitive match for the X-UA-Compatible header.
What was the issue?
The existing implementation compared the header value using a case-sensitive check, which caused valid values such as:
X-UA-Compatible: IE=edge
to incorrectly trigger warnings.
What does this PR do?
i) Introduces a proper case-insensitive normalization for header values
ii) Ensures all variants like IE=edge, Ie=EdGe, or ie=edge pass correctly
iii)Removes outdated note in documentation about case-sensitive limitations
iv) Updates README with clear explanation of new case-insensitive behavior
This improves correctness and aligns with Microsoft’s specification that the header is case-insensitive.
Issue reference
Fixes: #6028
Additional notes
-> No major logic changes beyond normalization.
-> Existing test suite may not require updates unless tests expect strictly lowercase matches.