-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Undefined' module header on safari < 11 #1897
Comments
i think that's the one d8b7292#diff-77ab163850ef0fa98d6a9ee9fb6bbcaf |
@tbouron is it possible to keep dynamic headers without adding them to the DOM and then hiding them? |
@sejka With the currently way the code handles this, I'm afraid not. The wrapper DOM for the headers is only generated when the module is first initialised, then whatever comes from It could be changed of course, but I didn't want to introduce too much changes. Hiding the wrapper DOM if |
i see, i just started remote debugging on ipad and can see that |
HTMLElement.style is supported from safari 11. https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/style Maybe adding some polyfills or using |
@sejka clearly the I would be interested to know what the |
@tbouron just submitted pr, code is fine it's just not compatible with safari < 11 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey guys,
So i use MM as server only set up in a docker container and an old ipad as a screen. After last couple updates i noticed that my setup is all messed up with
UNDEFINED
headers above every module. So i check it on my laptop (chrome, w10) and everything is fine. Then i checked it on an iPhone (current ios) and also everything is fine. Thought this might be browser support issue so i tried browserstack.com for legacy safari versions and sure enough:Safari 11.1:
Safari 10.1:
Safari 9.1:
I don't know if thats really a large issue for the whole community or how much we want to support older browsers but sure enough it worked fine circa december 2019. Thanks!
The text was updated successfully, but these errors were encountered: