Opened 8 years ago
Closed 8 years ago
#40198 closed defect (bug) (fixed)
Customize: all previewable links are blocked in the customize preview on IE11
Reported by: | celloexpressions | Owned by: | westonruter |
---|---|---|---|
Milestone: | 4.7.4 | Priority: | low |
Severity: | normal | Version: | 4.7 |
Component: | Customize | Keywords: | has-patch has-screenshots commit fixed-major |
Focuses: | Cc: |
Description
Edge is fine, but on IE11 all previewable links are identified as blocked with cursor: not-allowed
and the links not being navigable. Probably only worth fixing if it's an easy fix - IE is generally on the way out in favor of Edge.
Attachments (1)
Change History (16)
#2
@
8 years ago
- Milestone changed from Awaiting Review to 4.7.4
- Owner set to westonruter
- Status changed from new to accepted
- Type changed from enhancement to defect (bug)
#3
@
8 years ago
- Keywords has-patch added; needs-patch removed
Looks like it's a remaining issue from #38409, where IE11 is adding the port number unexpectedly. 40198.0.diff strips off the default port of :80
which should resolve this issue. It fixes it for me in my tests on an IE11 VM.
@celloexpressions can you confirm?
This ticket was mentioned in Slack in #core-customize by westonruter. View the logs.
8 years ago
This ticket was mentioned in Slack in #core by swissspidy. View the logs.
8 years ago
#7
@
8 years ago
- Keywords has-screenshots commit added; needs-testing removed
Screenshot of the reproduced issue on Windows 10 - IE 11:
Tested 40198.0.diff on a native Win 10 - IE 11 and links in the preview work perfectly.
#8
@
8 years ago
This issue was reported to Microsoft as well:
[IE11 & scripting] Value of HTMLAnchorElement.host differs between script-created link and link from document
#10
@
8 years ago
- Keywords fixed-major added
- Resolution fixed deleted
- Status changed from closed to reopened
Re-opening for consideration in 4.7.4
#12
@
8 years ago
- Keywords fixed-major removed
- Resolution fixed deleted
- Status changed from closed to reopened
Per @mattwiebe in #38409:
Found another "fun" bug related to this in IE11 for
https
sites: the:443
port also gets spuriously added, causing thepostMessage
bridge to fail.
Patch incoming, can move this to a new issue if needed, but this is where the work for port 80 was already done.
See https://core.trac.wordpress.org/attachment/ticket/38409/38409.3.diff
Seems like a definite bug that should be fixed. Downloading an IE11 VM now.