Closed DahmaniAdame closed 1 year ago
Seems that we should be recommending a more specific keyword to exclude the inline script then? Like var DIVI
?
Agree with @webtrainingwheels
Let's keep this open to see if we receive any positive feedback about that from our customers.
Making the exclusions case sensitive also increases the chances of user input errors, if the user mistyped something with/without the correct casing
Good catch @webtrainingwheels. I was in the middle of it. I overlooked that detail 😅. But it will only fix the Divi situation cited as an example. Updated the Delay JavaScript Execution Exclusions. We can't control how users will enter their exclusions. A case sensitive exclusions will surely be a plus for the Delay JavaScript Execution.
Making the exclusions case sensitive also increases the chances of user input errors, if the user mistyped something with/without the correct casing
It's a risk, yes.
I would argue that a mismatch won't be necessarily be site breaking and easier to debug vs. non-obvious false positives that might break other things that the customer is initially focusing on, and would be harder to make a link to them while debugging.
We don't have enough cases to justify any action, though.
For more than one year we have no feedback about that from customers and no real examples where this is necessary. Let's close it and we'll reopen when there's a justified reason for that.
Before submitting an issue please check that you’ve completed the following steps:
3.10.5.1
Describe the bug The current Delay JavaScript Execution won't consider case sensitive strings. Which will exclude anything that matches the pattern, and consequently exclude items that weren't targeted by the exclusion.
This might also create dependency errors sometimes.
A good example is the Divi suggested exclusions for UX purposes.
The
DIVI
keyword is meant to exclude this specific inline script:But it ends up excluding anything that has
divi
on its filename or code.To Reproduce Steps to reproduce the behavior:
Divi theme
DIVI
Expected behavior We should be able to target specific scripts by using case sensitive keywords/phrases, with no false positives.
Screenshots N/A
Additional context Behavior noticed in this case - https://secure.helpscout.net/conversation/1747586547/317449/
Backlog Grooming (for WP Media dev team use only)