Problem/Motivation
#769936: .ajax-progress divs floating problem is resolved for D8 but we have the following code in views_ui.admin.theme.css
/**
* Drupal core forces AJAX triggering elements to float left when they are
* disabled due to AJAX processing. On the add view page, we have inline
* containers where we don't want that behavior; it causes the select dropdown
* which is triggered to jump to the left while the AJAX throbber is active.
*
* See also http://drupal.org/node/769936 (Drupal core issue); when that is
* fixed it may no longer be necessary to do this.
*/
.views-admin .container-inline .progress-disabled {
float: none;
}
Perhaps we can remove it?
Proposed resolution
Remove css.
Remaining tasks
Task | Novice task? | Contributor instructions | Complete? |
---|---|---|---|
Create a patch | Y | Instructions | |
Manually test the patch | Y | Instructions | |
Embed before and after screenshots in the issue summary | Y | Instructions | |
Review patch to ensure that it fixes the issue, stays within scope, is properly documented, and follows coding standards | Instructions |
User interface changes
None
API changes
None
Comment | File | Size | Author |
---|---|---|---|
#9 | 7-9-interdiff.txt | 1.11 KB | alexpott |
#9 | 2315015.9.patch | 4.43 KB | alexpott |
#7 | 2315015.7.patch | 4.22 KB | alexpott |
#2 | 2315015-Remove-AJAX-throbber-jumping-prevention.patch | 904 bytes | gauravkhambhala |
Comments
Comment #1
gauravkhambhala CreditAttribution: gauravkhambhala commentedI will create patch to remove above code.
Comment #2
gauravkhambhala CreditAttribution: gauravkhambhala commentedUploading patch here.
Comment #3
alexpott@gauravkhambhala in order to get the testbot to review the patch you need to set to needs review. But far important with this one is some sort of evidence that the throbber does not make the views ui jump since that is what the comment is saying that the removed CSS prevents.
Comment #4
gauravkhambhala CreditAttribution: gauravkhambhala commented@alexpott I didn't really see what has been fixed by removing css in add views page. Please check the this screencast https://www.youtube.com/watch?v=XlENTsYHR-U This has been captured after applying the patch above. Let me know if anything else to test.
Comment #5
longwaveThis looks good to me, the CSS is no longer required and there is no difference before or after.
There is suspiciously similar but uncommented code in views.module.css:
Comment #6
gauravkhambhala CreditAttribution: gauravkhambhala commented@longwave Any action required on the code that you mentioned in views.module.css?
Comment #7
alexpott#1989480: Progress Bar style update and #1280674: Submit button "floats" during ajax submission have removed all stylings on of progress-disabled class. Therefore I think we can completely remove it.
Comment #8
longwaveThis looks strange after the line in the middle is removed. Otherwise I think this is good to go.
Comment #9
alexpottOkay-dokey - in fact the create of the $throbber variable looks unnecessary.
Comment #10
nod_I could see how one would use the class for some custom styling but I'll let a themer say whether that class makes sense to keep or not (because using prop I'm pretty sure css like
[diabled]
won't work).As far as JS is concern I'm ok with it. If the class is not needed, feel free to RTBC.
And thanks for the tag :)
Comment #11
longwaveI think both
[disabled]
and:disabled
are valid CSS selectors for elements with the disabled property, actually. We already use:disabled
in Seven's buttons.theme.css.Comment #12
nitishchopra CreditAttribution: nitishchopra commented#9 patch applied succesfully and the instances of "progress-disabled class" are removed.
Comment #13
jOksanen CreditAttribution: jOksanen commented#9 Applies and the functionality works perfectly. Marking as RTBC. Coding standards are followed.
Comment #15
webchickYay, less code! Good hunting. :)
Committed and pushed to 8.0.x. Thanks!