You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
The issue still exists against the latest master branch of bootstrap-fileinput.
This is not an usage question. I confirm having read the plugin documentation and demos.
This is not a general programming / coding question. (Those should be directed to the webtips Q & A forum).
I have attempted to find the simplest possible steps to reproduce the issue.
I have included a failing test as a pull request (Optional).
Libraries
bootstrap-fileinput version: 5.2.4, 5.2.5
The change introduced in this commit - 22ce1ed#diff-336f513b57ac7d4ac2af892a5fdc467725efd1b7c47b3eaa2ec64fbb6935f2da
makes the component fail when running tests with webpack and karma, because document.currentScript property is null in such environment. It would be great if some fallback could be provided (e.g. returning empty string from getLoadingUrl() when currentScript is null). I've tried to workaround the issue but without success.
Unfortunately I can't provide a simple example to reproduce the problem.
The text was updated successfully, but these errors were encountered:
It would be great to have new release. I have reports from users of my framework, which uses your component with webpack, they are affected by this issue not only in tests. Thank you for all your effort!
Prerequisites
master
branch of bootstrap-fileinput.Libraries
The change introduced in this commit - 22ce1ed#diff-336f513b57ac7d4ac2af892a5fdc467725efd1b7c47b3eaa2ec64fbb6935f2da
makes the component fail when running tests with webpack and karma, because
document.currentScript
property is null in such environment. It would be great if some fallback could be provided (e.g. returning empty string fromgetLoadingUrl()
whencurrentScript
is null). I've tried to workaround the issue but without success.Unfortunately I can't provide a simple example to reproduce the problem.
The text was updated successfully, but these errors were encountered: