Closed (fixed)
Project:
Drupal core
Version:
8.8.0
Component:
javascript
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2019 at 13:44 UTC
Updated:
30 Dec 2019 at 11:54 UTC
Jump to comment: Most recent
Comments
Comment #2
andrey_semenoff commentedComment #3
bnjmnmI'm moving the priority from Critical to Normal as this is likely specific to the specific Drupal installation of the reporter, and not something impacting all core users. This is not to dismiss the fact that it could very well be critical to the site being updated, but this would not be considered critical until there was evidence that this is truly a Drupal core issue.
This is based on no other users reporting the issue, that core's many FunctionalJavascript tests are passing, and it's not clear how to reproduce this on a fresh Drupal install.
The steps to reproduce on a fresh install is the most important part as that is what a developer would need to identify and address the bug, and it would prove it's a core issue vs. something site-specific.
To help narrow things down, perhaps you can try uninstalling contributed modules on a local instance, to rule out a compatibility issue with one of those?
Comment #4
longwaveAny JavaScript errors shown in your browser console would also be helpful in tracking this down.
Comment #5
andrey_semenoff commentedOk, guys, thanks for your comments.
It was my first issue here, so might be I've made some mistakes while creating it.
After some time of investigation of this issue - finally I've found the reason.
Might be my answer will be helpful for someone.
I'm using module ADVANCED CSS/JS AGGREGATION for loading time optimization.
This basic module has some additional modules that extends its functionality.
One of them is called AdvAgg Modifier. It has some settings, one of them was the reason of problems, described in this topic.
Setting is situated in group ADJUST JAVASCRIPT LOCATION AND EXECUTION (Deferred JavaScript Execution: Add The defer Tag To All Script Tags), and after I set it to Disabled - all problems have been gone.
Issue can be closed.
Comment #6
longwaveThanks for the update, I am glad you managed to resolve the issue.