Dropbutton field pushed out of the table if no label set

FYI once one set of screenshots is added additional screenshots are duplicative work.

Reviewing the patch believe we are trying to get away from using dir="rtl"

Tried testing on claro but I didn't see the issue. Maybe additional steps should be added?

I also tried testing on both claro and seven themes, however issue is not reproducible on 10.1.x-dev.

#46 and #47 were unable to replicate the issue so adding a tag

Added standard IS template which was missing.

The issue of Global dropdown getting pushed out of the table does not seem to be reproduced in 11.x, but new issues has taken its place altogether.

Steps taken to reproduce the issue taken from #28.

1. In single field dropdown is selected,

a. It follows standard when text character length is normal without too much spacing.

b. It follows standard when text character length is not normal without any spacing between words in dropdown button

c. It does not follow when text character length is long and has spacing between words.

2. In multi field dropdown selection,

a. It follows proper spacing standards in relation to other table rows only when Content: Node operations bulk form is selected

Bulk form view:




Bulk form dropdown open:




b. It breaks standard view if any other field besides Content: Node operations bulk form is selected and when the first field contains anything unique such as Title, Author Name



Standard redirect dropdown broken view:



Transparent dropdown broken view:


c. It breaks standard view when any field that cannot be redirected is selected; these fields are visible with a transparent bg, without following any spacing, positioning standards. Similarly if fields that can be redirected appear they appear normally.



Normal drop multi field:



Bulkdrop multi field:

The new issue that seem to appear are :

1. If single field dropdown is selected,

a. It follows standard when text character length is normal without too much spacing.

b. It follows standard when text character length is not normal without any spacing between words in dropdown button

c. It does not follow when text character length is long and has spacing between words.

2. In multi field dropdown selection,

a. It follows proper spacing standards in relation to other table rows only when Content: Node operations bulk form is selected

Bulk form view:




Bulk form dropdown open:




b. It breaks standard view if any other field besides Content: Node operations bulk form is selected and when the first field contains anything unique such as Title, Author Name



Standard redirect dropdown broken view:



Transparent dropdown broken view:


c. It breaks standard view when any field that cannot be redirected is selected; these fields are visible with a transparent bg, without following any spacing, positioning standards. Similarly if fields that can be redirected appear they appear normally.



Normal drop multi field:



Bulkdrop multi field:

The original issue mentioned in this ticket

Dropbutton field pushed out of the table if no label set

is not reproducible in Drupal version 11.x. Attaching screenshots for reference.

But as mentioned in #52 🐛 Dropbutton field pushed out of the table if no label set Needs work , there are UI issues when a field which cannot be redirected is added in the Global dropdown (SS can be referred in #52).
In the Global dropdown configuration, all the fields which are added in the view are listed down as options for global dropdown items. Also, there is a help text saying "Fields to be included as links." which doesn't make sense because fields such as Content Type, Status, Updated, etc doesn't have any link to redirect, so why do we have to show those fields as an option for global dropdown? Also Operations field which is already a dropdown should not be allowed as an item in another dropdown right? (I'm checking this in /admin/structure/views/view/content)

Please correct me if I'm getting this wrong. If we need to work on dropdown style, then I think it should be tracked in a different ticket since the original issue of this ticket is already fixed in D11. Marking this as Needs Review for feedback from others.

Issue summary still appears to be incomplete/incorrect.

No steps to reproduce
No proposed solution
Broken images in release notes (this doesn't need release notes as it's not a major change)