-
Notifications
You must be signed in to change notification settings - Fork 68
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splitting breaks when called from inside IIFE #41
Comments
A PR is welcome, but changing the dist/ files isn't a permanent solution as those are generated files. It would break the next time the code was re-compiled. What situation is Splitting being included in where it isn't in the global scope? |
I am curious how you're running Splitting to get this error.
One thing to be aware of as well: Splitting is dependent on `document`
methods/properties for generating elements, so it will error out if you try
to call it without `document` being available.
Check out issues #20 and #28 for some discussion on this
#20
#28
…On Tue, Jul 30, 2019 at 10:48 PM Christopher Wallis < ***@***.***> wrote:
A PR is welcome, but changing the dist/ files isn't a permanent solution
as those are generated files. It would break the next time the code was
re-compiled.
What situation is Splitting being included in where it isn't in the global
scope?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=AAF5XQZZ7FHG3IDR6HJEYT3QCEDR7A5CNFSM4IH2CFCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3F7LJI#issuecomment-516683173>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF5XQ55QOBQF3ZGOYETSEDQCEDR7ANCNFSM4IH2CFCA>
.
|
document is available but (function() {
Splitting();
})(); so the line |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because it assumes
this
will always bewindow
here:When called in a scope other than the global scope, it breaks. I can send in a PR with this change
The text was updated successfully, but these errors were encountered: