React version: 16.12
Sometimes an "Unspecified error" will appear in the console and the viewer in the iframe won't load

Unfortunately it is not 100% reproducible. Sometimes the error won't occur. I'm also having trouble creating a minimal sample to reproduce this.
There is no error.
The relevant line in the callstack where the error is occurring is here https://github.com/facebook/react/blob/03de849af03996b7477420c97de7741ce1214149/packages/react-dom/src/client/ReactDOMInput.js#L415
I suspect it might be the same issue discussed here https://github.com/Availity/react-block-ui/issues/18
This was a real pain to track down, but apparently IE 11 will just throw Unspecified error. when accessing document.activeElement from an
The solution they used to fix the error was to use this function instead of accessing document.activeElement directly https://gist.github.com/Alex1990/046a6553dc83e22dd6f4
Ideally this function could be used inside React as well. I am also happy to use a workaround if there is one.
is anyone working on this? or can i give it a shot?
@dhavalsingh are you working on this issue?
Hi, is this issue available? If yes, I wanna take it up as my first issue to the React project. Thanks!
Hi @hemakshis, I was waiting for @dhavalsingh to reply. I think you can go for it. I can help if needed.
@hemakshis All yours. If you get stuck at any point in time feel free to share your progress.
Thanks a lot @pfongkye and @eps1lon. Will definitely reach out if I face any issues.
Hi, I am unable to reproduce this error, can someone help me with it? And how can I contact you - Discord, IRC, or some other means?
Thanks.
Hi, I am unable to reproduce this error, can someone help me with it?
Looking at the initial issue description this might be tough to accomplish:
Unfortunately it is not 100% reproducible. Sometimes the error won't occur. I'm also having trouble creating a minimal sample to reproduce this.
I guess @bvaughn envisioned that this could just be solved by replacing the current read with https://gist.github.com/Alex1990/046a6553dc83e22dd6f4.
But reproducing a IE11-iframe bug that only "sometimes" occurs seems like a pretty hard task to me.
Hi,
Thanks for your inputs. I was going through the code and found that there is already a very similar implementation done in this file:
getActiveElement.js
https://github.com/facebook/react/blob/c641b611c4d270660b0bb850759f5a324787a7b3/packages/react-dom/src/client/getActiveElement.js#L10-L20
This function is being called in a few places but not where the reporter has mentioned the change needs to be done. I think we can reuse this function in mentioned line of description. Please let me know if this sounds correct or not.
Hi,
Created #19664
Request you to please review it.
Thanks
Hi @pfongkye, @eps1lon, I want to continue contributing so do you think I can take up some other issue, if yes, please let me know? Maybe not as trivial as this one.
Closed in #19664
Hi @pfongkye, @eps1lon, I want to continue contributing so do you think I can take up some other issue, if yes, please let me know? Maybe not as trivial as this one.
You can look through the issues marked as "bug" and see if something catches your eye. The conversations might have some hints how a fix might look or whether this this isn't worth fixing because an upcoming refactor might fix it incidentally.
Also triaging issues or simply checking if they're still valid or need an updated reproduction is a form of contributing as well.