#44742 closed defect (bug) (wontfix)
Try Gutenberg Callout: Positioning falls apart in IE11
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.9.8 |
Component: | Administration | Keywords: | has-screenshots |
Focuses: | ui | Cc: |
Description
Attachments (3)
Change History (21)
#3
in reply to:
↑ description
@
7 years ago
Replying to kjellr:
Tested with:
Windows 7, IE 11.0.9600.17420
WordPress 4.9.8
Update to IE11 11.0.9600.19035 via windowsupdate or visit https://browsehappy.com/
#4
@
7 years ago
@luciano-croce:
I updated to IE11 11.0.9600.19080 and the problem persists.
I tested on a fresh site as well and see the issue there.
#5
@
7 years ago
- Keywords needs-patch added; needs-testing removed
Please disregard my previous comment and screenshot. I was using Microsoft Edge with Dev Tools IE11 emulation. Using IE11 I can confirm the issue as well.
#7
@
7 years ago
I just updated to the latest version of IE11 and I am still seeing the Try Gutenberg sections overlapping each other. It has to do with IE11 not supporting all of the newer css grid specifications, see https://stackoverflow.com/questions/45786788/css-grid-layout-not-working-in-edge-and-ie-11-even-with-ms-prefix#answer-45787093
#8
@
7 years ago
- Component changed from General to Administration
- Milestone changed from Awaiting Review to 4.9.9
This ticket was mentioned in Slack in #core by swissspidy. View the logs.
7 years ago
#10
@
7 years ago
I see the issue on IE 11.540.15063.0 on Windows 10. WordPress version 4.9.8.
I am using the Browserstack Windows 10 IE 11 vm.
#12
@
7 years ago
Here's a patch to fix this. Worth noting the Gutenberg panel isn't in origin/master, only origin/4.9, so that's what this diff is made from. My understanding is origin/master should be the trunk.
IE 11 is using flexbox, grid properties were moved into @supports.
#13
@
7 years ago
@kjellr or @ianbelanger can you confirm this patch fixes the issue you were seeing?
Hi @kjellr,
I just tested this on Windows 10 machine using IE11 and IE10. I could not reproduce the issue that you are seeing. I wouldn't think that the OS would affect the way a browser renders the page, but maybe, I guess.