Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.See the attached screenshot. "Show row weights" does not show the weights, and it does hide the drag handles. "Hide row weights" restores the drag handles.
| Comment | File | Size | Author |
|---|---|---|---|
| Screen Shot 2013-05-18 at 3.35.11 PM.png | 194.13 KB | Anonymous (not verified) |
Comments
Comment #1
btopro CreditAttribution: btopro commentedgotcha, maybe we need to disable them entirely but I'm not sure about doing so because of accessibility. patch welcome
Comment #2
btopro CreditAttribution: btopro commentedaccessibility issue, they need to be there
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedI don't understand. The bug is that "Show row weights" does not, in fact, show the row weights.
Comment #4
btopro CreditAttribution: btopro commentedI'll accept a patch to clean up this usability error but this module doesn't really degrade well since it is doing ajax based submissions of something that you can do in a more accessible manner for row weights when outline designer is disabled. How would you suggest handling the item?
Comment #5
Anonymous (not verified) CreditAttribution: Anonymous commentedI would suggest removing the functionality if there's no plan to make it work. Having a button that doesn't do what it says, or in fact much of anything at all, is confusing for users.
Comment #6
btopro CreditAttribution: btopro commentedhmm.. looking into it I'm not sure how best to handle it. Basically you could cause the form to be inoperable under certain conditions.
Example: Go to the menu or block pages, click the button that has this same description to "show row weights". Now come back to the outline designer and the functionality of it is effectively removed. This isn't to say there aren't ways around this / improving it / accounting for it; just that it'll require some deeper investigation then just hiding it via CSS / removing from the interface.
Comment #8
btopro CreditAttribution: btopro commentednabbed it. should be fixed in dev now without conflicting elsewhere.