orakili

Results 6 comments of orakili

Success/Error callbacks never called when the script element has the "nomodule" attribute.

Both options seem reasonable and on modern browsers would have the same effect (script ignored). Another option could be to load the nomodule script but call the `callbackFn` directly to...

Success/Error callbacks never called when the script element has the "nomodule" attribute.

That's an interesting new feature to explicitly indicate how to load a script. Unfortunately that would not solve the issue for implementations currently adding attributes to the script element via...

Success/Error callbacks never called when the script element has the "nomodule" attribute.

I would not expect a fast response to the Drupal issue. The scenarios in which case a Drupal site would be affected by the issue are limited so I'm not...

Success/Error callbacks never called when the script element has the "nomodule" attribute.

I think it meant still being able to add a script without the `module!` path modifier, like in the current version of loadjs: ```javascript loadjs(['/path/to/foo.mjs', 'module!/path/to/bar.mjs', 'nomodule!/path/to/foobar.js'], { // Load...

Success/Error callbacks never called when the script element has the "nomodule" attribute.

Sounds good.

Success/Error callbacks never called when the script element has the "nomodule" attribute.

Thanks. I tested the 4.3.0-rc1 version with the following `['module!dep1.js', 'nomodule!dep2.js', 'dep3.js']` in different browsers and got the expected results: - Recent Safari, Chrome, Firefox, Edge etc.: dep1 and dep3...