Opened 9 years ago
Closed 9 years ago
#12149 closed defect (fixed)
MSIE10 bug: "#__msie303:" not being replaced to "#" on client side
Reported by: | Owned by: | Jun Omae | |
---|---|---|---|
Priority: | normal | Milestone: | 1.0.9 |
Component: | general | Version: | 1.0.8 |
Severity: | minor | Keywords: | iexplorer10 |
Cc: | Branch: | ||
Release Notes: |
Fix broken |
||
API Changes: | |||
Internal Changes: |
Description
Following on from #11262 and as reported in this thread:
On my system the comment links are broken (with __msie303:
), due as far as I can tell to corporate instance on compatibility mode.
https://server.name/shared/sand-pit/ticket/2#ticket
Adding a comment:
https://server.name/shared/sand-pit/ticket/2#__msie303:comment:1
Editing the comment:
https://server.name/shared/sand-pit/ticket/2?cnum_edit=1
…resulting in:
https://server.name/shared/sand-pit/ticket/2#__msie303:comment:1
(again)
Server: Trac 1.0.8 on Windows 2008R2, self-built apache httpd 2.4.12, mod_wsgi 4.4.11 and Python 2.7.9 Client: Windows 7 enterprise using IE10
Ticket opened at request of Jun Omae:
However, I reproduce that issue when Trac site matches compatibility mode settings. It seems that X-UA-Compatible can override document mode but cannot override the behaviour for
__msie303
trick.
Attachments (0)
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Keywords: | navigation msie303 removed |
---|---|
Milestone: | → next-stable-1.0.x |
I've already tested. Both X-UA-Compatible
header and meta tag lead standard mode in rendering. However, this issue isn't solved.
comment:3 by , 9 years ago
Milestone: | next-stable-1.0.x → 1.0.9 |
---|---|
Owner: | set to |
Status: | new → assigned |
Proposed changes in [85c569407/jomae.git] ([log:jomae.git@t12149). After the changes, it wouldn't use the __msie303
trick for IE 10 and 11 even though compatibility view mode.
comment:4 by , 9 years ago
Keywords: | iexplorer javascript removed |
---|---|
Release Notes: | modified (diff) |
Resolution: | → fixed |
Status: | assigned → closed |
I did find one possible fix which suggests setting
X-UA-Compatible
as a header, not in the response body:https://bibwild.wordpress.com/2014/09/02/defeating-ie-forced-compatibility-mode/