The IE does not seem to support all "new" JavaScript techniques, so there is a JS error. Unfortunately, this prevents the loading of this module and there is no indication that the browser is out of date. Is it possible that this module is loaded first of all before anything else?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | fix-for-ie11.patch | 335 bytes | cpierce42 |
Issue fork bu-3154405
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
cweagansThe attached patch changes the order of the bu JS that's added to the page to be after `drupal/core` and `drupal/coreSettings`, but before everything else, thereby allowing the bu JS to run before any new JS syntax cause JS to stop executing.
This is a somewhat fragile solution (as it will break if the weights are changed in core.libraries.yml), but given that those weights haven't changed since Drupal 8, I'm inclined to think that it's workable for now. The weights for the core JS are hardcoded in core.libraries.yml, so I went with 15 to ensure the correct ordering.
Comment #3
cpierce42Pulled down the patch, tested and this patch did not work.
Comment #4
cpierce42This patch fixes the problem for me in IE, loading the JavaScript in the header without manipulating the weights.
Comment #5
luiscarvalho commentedThe patch above is likely to work, but if AdvAgg is used and it does not work, you can remove the BU library from preprocess on other module:
Comment #6
cpierce42Comment #5 does not fix the problem for me and I am not using AdvAgg module.
Please review/test #4