Skip to content

Portal: recent change breaks in IE11 #2886

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

Closed
traverse opened this issue Jun 6, 2018 · 5 comments · Fixed by #2958
Closed

Portal: recent change breaks in IE11 #2886

traverse opened this issue Jun 6, 2018 · 5 comments · Fixed by #2958
Labels

Comments

@traverse
Copy link
Contributor

traverse commented Jun 6, 2018

Bug Report

A change introduced in #2657 to the portal component causes an error in IE11 when trying to open anything using a portal.

The change:

this.rootNode.style = style || ''

Steps

Use anything with a portal in IE11 and try to open it.

Expected Result

Should open the portal.

Actual Result

Throws the following error:

SCRIPT5045: Assignment to read-only properties is not allowed in strict mode

Which points to the changed line.

Version

[email protected]

@ghost ghost added the triage label Jun 6, 2018
@layershifter layershifter changed the title Recent portal change breaks in IE11 Portal: recent change breaks in IE11 Jun 6, 2018
@layershifter layershifter added bug and removed triage labels Jun 6, 2018
@layershifter
Copy link
Member

Will be fixed in #2880.

@mgandley
Copy link
Contributor

@levithomason @layershifter per https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/style you could probably fix this with one line of code by changing this this.rootNode.style = style || '' to this this.rootNode.cssText = style || '' or this this.rootNode.setAttribute('style', style || '')

Not sure how much more work is needed for #2880. Considering this bug is affecting all portals for a major browser, this quick fix might be worth doing if it's going to be more than a few more days.

@mihai-dinculescu
Copy link
Member

I support an individual release of the fix. Currently my team is stuck with using version 0.80.2. Even if #2880 comes soon, it looks like a risky upgrade to do right after the release.

@layershifter
Copy link
Member

@mgandley @mihai-dinculescu Feel free to submit PR 👍

@mgandley
Copy link
Contributor

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants