In #1873342: Remove redundant/un-needed settings from views UI we noticed there was some discussion around removing "Disable JS for Views UI". One reason to keep it in currently, is because we need it for accessibility - however as we push towards the new jQuery UI this bug will be removed.
However its kind of a one-off function, we don't have elsewhere in core (e.g. there is no disable JS on Fields UI, and probally also won't on the layout UI). Having this setting for Views UI is therefor supporting a usecase, I don't really see existing beyond those developing for views.
Two reasons xjm, mentioned is that somehow Views UI can be really slow because of JS. But its also a easy function to debug modules that extend Views.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | interdiff-1874528-8.txt | 632 bytes | damiankloip |
| #8 | 1874528-8.patch | 3.97 KB | damiankloip |
Comments
Comment #1
damiankloip commentedAs in the other issue, +1 for this.
I don't think this should live in core, not for the purpose of easier debugging. A contrib module could in theory provide this pretty easily if they wanted to.
If it gets slow, that is something that should be looked at.
Comment #2
nod_tag
Comment #3
xjmLet's at least postpone this on the modals being accessible.
Comment #4
damiankloip commentedWhatever.
Comment #5
mgiffordThe modals are good. Is this issue still needed?
Comment #6
damiankloip commentedYes, we still need this. The modals should be good now, and degrade fine. Using this setting completely breaks views UI anyway. Let's rip it out.
Comment #7
dawehnerYou forgot to drop the javascript as well. DIC
Comment #8
damiankloip commentedComment #9
damiankloip commenteddaniel here: this is RTBC now. In general things like jquery update should solve the problem for their own.
Comment #14
mgiffordBelieve this was just the bot being a bit exhausted...
Still seems to apply easily.
Comment #15
alexpottCommitted 49eea51 and pushed to 8.0.x. Thanks!