Skip to content

Core: Handle IE11 bug with document.activeElement in iframes #1518

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

Conversation

scottgonzalez
Copy link
Member

Fixes #11539

How has this not come up before?

@jzaefferer
Copy link
Member

Looks fine, as in, I realize that being angry at IE doesn't help, so why not add more workarounds on top of existing workarounds.

@jzaefferer
Copy link
Member

@jacobrossi
Copy link

@jzaefferer @scottgonzalez do either of you know if this still repros in the EdgeHTML engine? if not, can you check at remote.modern.ie? I'll get a bug filed and prioritized if it does.

@scottgonzalez
Copy link
Member Author

@jacobrossi I'll be working on a reduced test case tomorrow and I'll test against remote.modern.ie at that time.

@scottgonzalez
Copy link
Member Author

It appears to work properly on remote.modern.ie. This is as far as I got for reducing it: http://jsbin.com/fejituname/1/

@jacobrossi
Copy link

Great, then that means it works OK in Project Spartan too. I realize that doesn't help you out with IE. But it's still good to see it's fixed nonetheless.

@scottgonzalez scottgonzalez deleted the ie11-activeelement branch March 26, 2015 18:49
scottgonzalez added a commit that referenced this pull request Jun 9, 2016
Fixes #11539
Closes gh-1518

(cherry picked from commit 76c2755)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants