-
Notifications
You must be signed in to change notification settings - Fork 47.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bug: "Unspecified error" some of the time in IE11 in iframe #19530
Comments
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. |
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? |
Looking at the initial issue description this might be tough to accomplish:
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, react/packages/react-dom/src/client/getActiveElement.js Lines 10 to 20 in c641b61
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, |
Closed in #19664
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. |
React version: 16.12
Steps To Reproduce
The current behavior
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.
The expected behavior
There is no error.
Investigation
The relevant line in the callstack where the error is occurring is here
react/packages/react-dom/src/client/ReactDOMInput.js
Line 415 in 03de849
I suspect it might be the same issue discussed here Availity/react-block-ui#18
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.
The text was updated successfully, but these errors were encountered: