- Notifications
You must be signed in to change notification settings - Fork855
Fix unreliablewindow
anddocument
detection#246
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Signed-off-by: Viktor Bezděk <viktor.bezdek@siteone.cz>
…ts published to fix ssr issuesSigned-off-by: Viktor Bezděk <viktor.bezdek@siteone.cz>
istarkov commentedSep 22, 2016 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Thank you!
|
I'll fix files in the repo in sec. Will let you know. |
The last commit is reverted. If you accept the pull request, please publish the patch asap. |
Thank you!!! Will publish today. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The method used for detecting DOM availability was sloppy and breaks server side rendering in some cases. This new approach fix cases when global variable window is defined in NodeJS by checking presence of
window.document
andwindow.document.createElement
which are used in element resize detection.