Please test the core patch to help fix this bug in Drupal core - Mark this module as obsolete when that happens

The module's front page should be edited/updated to include the following:

1. State (perhaps in bold):

This core bug has been fixed in D7: #179932: Required radios/checkboxes are not validated

I know there is a link to that issue already, but it is a simple link rather that a drupal issue link (that also displays issue status), it does not state that it is for D7 and it does not point to the exact post # that marks it as fixed (with any extra comments if available). The issue in question is quite long (157 posts at the time of writing this) and users might have to go through the whole list of comments in order to find more info. It is common for users going there and switching the issue to D6, which in turn might piss people off that have to switch it back each time. My suggestion corrects this by providing most of this info at a glance.

2. State:

This is the related D6 issue: #259292: Required radios/checkboxes are not validated (D6). More experienced users should head there and help fix this in core by testing the latest patch (instead of installing this module!)

Again the link to the issue is there, but it needs to be "dupalified", if I may use the term ;)

3. The note would be better if it pointed to this issue/task like so:

Note: developers don't need to add any extra validation code to their modules to make up for the bug in core, and once core is fixed this module can be uninstalled: #856452: Please test the core patch to help fix this bug in Drupal core - Mark this module as obsolete when that happens

...once again "dupalified" issue link to also show status.

I would be more than happy to edit the front page myself so to reflect all these proposed changes, but I have no permission to do it.

PS: this feels more like a task to me than a bug report. Right?

-edit: missed a couple of things here and here in my previous post, sorry for the noise-

Done.

...was that fast or what? ;)

Thanx.

...actually I think we should keep this issue open.

What was actually fixed is my suggestions were applied to the module's first page. I think this issue should stay here to serve as a pointer/reminder or at least it should be set to 'postponed'. Remember that its link is in the first page after the '...once core is fixed this module can be uninstalled:' and if its status changes to 'fixed'/'closed' then it might give people the wrong idea that the module is no longer needed.

Since (sadly) there is no way in drupal.org to mark issues as dependent to other ones, 'postponed' (...till another issue is fixed) seems the proper status for this IMHO.

...PS: I think/hope that there is some sort of automated process in drupal.org (cron run) that updates links that point to issues in order to reflect their current status. Or else this issue's status in the module's front page will remain 'needs work'. Again this will give the wrong impression that something needs to be done here.

If there is no such thing and the issue's link status remains 'needs work' after 24 or 48 hours, could you please do a quick edit/save and see if the status gets updated then?

Thanx in advance and sorry for/if being a balls-buster ;)

Subscribing.