Missing column headings in Revisions list

Created on 9 December 2016, over 8 years ago
Updated 8 May 2024, 11 months ago

Diff adds to columns to the Revisions list of a node, which get populated with radio buttons. However, since there are no headings to the columns it is completely unclear for the user what these buttons are supposed to do.

🐛 Bug report
Status

Needs review

Version

1.0

Component

User interface

Created by

🇫🇷France martin.knapp

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • 🇳🇿New Zealand ericgsmith

    Rebased the MR.

    We are using this patch and editors found it an improvement of the diff screen - I note there hasn't been much discussion on this since #11 so not setting to RTBC, although I can say I have one client happy using this approach.

  • Pipeline finished with Success
    11 months ago
    Total: 452s
    #166997
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Patch containing the current state of the merge request.

  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Sorry, ignore the patch in #22. This is the correct patch containing the current state of the merge request.

  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    @miro_dietiker: Perhaps the column labels should be "Compare revision A" and "Compare revision B" or "Compare from" and "Compare to".

    The question of the compare button on long forms is addressed in Add "compare revisions" button on top for long form. Needs review .

  • Pipeline finished with Failed
    11 months ago
    Total: 381s
    #172743
  • Status changed to Needs work 11 months ago
  • 🇦🇺Australia acbramley

    PHPStan is failing.

  • Status changed to Needs review 11 months ago
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Rebased. phpstan passes.

  • Pipeline finished with Success
    11 months ago
    Total: 460s
    #178274
  • Status changed to RTBC 11 months ago
  • 🇺🇸United States bkosborne New Jersey, USA

    +1 to the latest patch.

  • Status changed to Needs work 11 months ago
  • 🇦🇺Australia acbramley

    I'm not a huge fan of these column headings, and as stated already in the comments the A/B labelling may not make sense in other languages. With that being said, I don't really have any good alternatives but don't want to commit something before we get more of a consensus.

  • 🇳🇿New Zealand ericgsmith

    What about using "Source" and "Target"?

    I've been using Gitlabs compare revisions a lot - and I know the context and UI is different, but I feel like maybe the same label be adapted?

    E.g left column = "Source", right column = "Target"

    "Source" and "Target" then with something to explain it in the help text link:

    "When comparing selected revisions the changes are shown as if the source revision was being updated to the target revision."

    I have a few clients who often use this screen, I can ask them to review options if we can get a few other ideas in the mix.

  • 🇦🇺Australia acbramley

    @ericgsmith source and target definitely make more sense to me. I'd be happy with that.

  • Status changed to Needs review 11 months ago
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Perhaps it should be "Compare" instead of "Select" to make it clear that these are used for comparisons. I have rebased and updated the labels along these lines.

    For other languages, these are translatable strings, so it could be whatever is desired in that language.

  • Pipeline finished with Success
    11 months ago
    Total: 415s
    #179276
  • Status changed to Needs work 11 months ago
  • 🇦🇺Australia acbramley

    See MR comments.

  • Status changed to Needs review 11 months ago
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Rebased. All comment threads resolved.

  • Pipeline finished with Success
    11 months ago
    Total: 224s
    #187328
  • 🇦🇺Australia acbramley

    Sorry should've mentioned this needs to go into 2.x.

  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Rebased

  • Pipeline finished with Success
    10 months ago
    Total: 261s
    #189933
  • Status changed to Needs work 4 months ago
  • Hi @liam morland,

    I have replicated the issue and applied the patch you provided, confirmed the issue is solved, however, would it be possible to display the radio buttons at the center of the column. Please see images for reference.

    Thanks,
    Jake

  • The uncentered radio buttons

  • 🇮🇳India sandip

    Working on it.

  • 🇮🇳India sandip

    Please review it once.

  • Pipeline finished with Failed
    4 months ago
    Total: 302s
    #370935
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    Thanks for the patch.

    Those CSS selectors work to center the radio buttons, but they will change other tables too. It is probably needed to add .diff-responsive-table to the selectors.

  • Pipeline finished with Failed
    4 months ago
    Total: 127s
    #372165
  • 🇮🇳India sandip

    Updated css file but i did not find .diff-responsive-table class in table instead it is .diff-revisions.

  • Hello @sandip poddar,

    Thank you for your contribution to resolving the issue. After applying your changes locally and testing the implementation, I found that the issue is not fully resolved as expected.

    I have attached before and after screenshots for your reference, which highlight the areas where the issue persists or behaves unexpectedly. Based on this, I have moved the issue to the "Needs Work" state.

    Please review the feedback and the screenshots to make the necessary adjustments. Let me know if you need further clarification or if you'd like to discuss any of the observations.

  • 🇮🇳India sandip

    I am looking into it.

  • Pipeline finished with Success
    3 months ago
    Total: 217s
    #408975
  • 🇮🇳India sandip

    The issue was caused by an inline display: block; style applied to the radio button input. I have resolved this by adjusting the styling accordingly. Please review the changes and let me know if any further modifications are needed.

  • Hello @sandip poddar,

    Thank you for your contribution to resolving the issue. After applying your changes locally and testing the implementation, I found that the issue is working as expected. So I am moving it into RTBC.

Production build 0.71.5 2024