Contrib.social

Table sticky actions not sticky

Open on Drupal.org →
Created on 23 November 2023, 8 months ago
Updated 2 January 2024, 6 months ago

Problem/Motivation

We're not sure if this change was intentional or not, but noticed when attempting to update from RC3 to RC5 a while back, that the content overview page (/admin/content) has changed behavior when you check an item in the list. This seems to still be the case in EC7.

Steps to reproduce

Visit the /admin/content page and check an item.
- In RC3, the actions section becomes sticky to the bottom of the page.
- In RC5+, the actions section DOES NOT become sticky to the bottom of the page.

Proposed resolution

On a long list of items, it feels like it might be confusing for authors as to what is going to happen when they select item(s) as the actions are not visible.

🐛 Bug report
Status

Closed: works as designed

Component

User interface

Created by

🇨🇦Canada tdroden Calgary, Alberta

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @tdroden
  • Status changed to Postponed: needs info 8 months ago
  • Comment 8 months ago →
    🇨🇭Switzerland saschaeggi Zurich

    I can't reproduce this issue on either Drupal 9 nor 10.

  • Comment 8 months ago →
    🇨🇦Canada tdroden Calgary, Alberta

    Oh, interesting. I'm seeing the issue on our Drupal 9.5.11 sites, and even a simple vanilla Docker instance running Bitnami Drupal 9.5.11 that I set up strictly for testing Gin. It works fine for RC3, but anything after and it stops working for us. I'm just not seeing the is-sticky class (or the newer data-drupal-sticky-vbo="true") being set when expected.

    But with your feedback, I spun up a simplytest.me instance and can indeed see it working there as expected.

    I'll do some more poking about to see if I can suss out the source of our issue. Thanks.

  • Status changed to Closed: works as designed 6 months ago
  • Comment 6 months ago →
    🇨🇦Canada tdroden Calgary, Alberta

    I haven't been able to determine a root cause for us. Since this appears to be an 'us' issue and we'll be updating to Drupal 10 soon (where it seems to work again) I think it is safe to just close this support ticket. Thanks!

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024