Closed (fixed)
Project:
Upgrade Status
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2020 at 14:26 UTC
Updated:
17 Sep 2020 at 09:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
nsalves commentedComment #3
nsalves commentedComment #4
gábor hojtsyCurrently it is a "label for" element, which means when you click it it will check the checkbox. Now that would only be true for custom projects. Not sure that is a good idea. Did you try the 8.x-3.x branch where it has an issue queue link even if there was no Drupal 9 plan information?
Comment #5
nsalves commentedHi Gábor
Thank you for your reply. Yes, I used the 8.x-3.x branch to build the patch (although I just checked that the patch no longer works since it seems some changes were made).
I checked and when the user clicks on the project name the checkbox don't becomes checked so this don't seem to interfere with that (or maybe I didn't understand your point).
I think the issue queue link serves a different purpose since it links to the issue queue and not the project main page which is the feature this patch tries to address. If you believe there's value adding this link I can submit a new version against the current version of the dev branch. Anyway thanks for your reply and apologies if I made any mistake in this process (first time committing a patch).
Comment #6
gábor hojtsyWell, if clicking on the label does not check the box that is definitely a bug then. That is the whole point of making it a label element and the
forattribute data provided below. It may become incorrect with the reshuffling of the elements.See https://stackoverflow.com/questions/18432376/what-does-for-attribute-do-...
Comment #7
nsalves commentedAfter your explanation I went back to the code and the problem appears to be related with an error on the name of the for attribute. It should be the same as the id of the checkbox element to work as you explained. Here's a patch to fix that. With this fix the feature I suggested no longer makes sense. Thank you.
Comment #8
gábor hojtsyThat is the direction indeed that we need to go IMHO to fix what was already working before. The group is not always relax though, this part of the ID needs to be dynamic.
Comment #10
gábor hojtsyCommitted an extended fix that passes on the machine name of the next step. Thanks!
Comment #12
gábor hojtsy@Kristen Pol also found this in #3165529: Various feedback on 8.x-3.x, crediting her too.