We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When selectize is used in an iframe with display:none, it throws an error. It's due to this long-standing bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=548397
display:none
The JS console says:
TypeError: window.getComputedStyle(...) is null selectize.min.js:2
The error is due to this line: https://github.com/brianreavis/selectize.js/blob/6a071a2809802176ebc01703b98109784ec5b931/src/selectize.js#L7
In particular:
window.getComputedStyle(input, null).getPropertyValue('direction')
In the hidden iframe situation, window.getComputedStyle(input, null) returns null, but another function call is chained after it.
window.getComputedStyle(input, null)
We've encountered this error on a different project, and our workaround is here: rstudio/shiny#550
The text was updated successfully, but these errors were encountered:
Safer way of getting rtl environment. Fixes selectize#520
cfa5610
This is a workaround for a Firefox bug, where window.getComputedStyle() returns null in an iframe with display:none. https://bugzilla.mozilla.org/show_bug.cgi?id=548397
b6ac02b
4712d00
2d22156
No branches or pull requests
When selectize is used in an iframe with
display:none
, it throws an error. It's due to this long-standing bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=548397The JS console says:
The error is due to this line:
https://github.com/brianreavis/selectize.js/blob/6a071a2809802176ebc01703b98109784ec5b931/src/selectize.js#L7
In particular:
In the hidden iframe situation,
window.getComputedStyle(input, null)
returns null, but another function call is chained after it.We've encountered this error on a different project, and our workaround is here:
rstudio/shiny#550
The text was updated successfully, but these errors were encountered: