thanks for your reply !
this is not the same request but for nearly the same need.
if you solve the issue RF-578, it won't solve my need.
personally i don't consider that as a bug/issue, it's more a feature-request/evolution.
being able to put multiple id in the for attibute can be useful for other case.
in my case it's adding a 'status' attribute on the region tag. because the status tag is automatically inserted in each page at the end and it don't knows how many regions the page contains nor their ids. Also I would make some specific region that won't use the general status.
in some very specific case where we would have multiples status for a region, i think the developper must avoid it and review his code, an error message should occur (like it's already the case but it says duplicateComponentId).
As i don't know how it's implemented, i can't judge the difficulty of the evolution, maybe later i'll have a look on this.
If it's possible to do this without using status component, i would like to know how...
not the same request, not exactly the same need... but it can be the same bug that prevent from doing it, i'm ok on this point.
we could also add a boolean attribute on the status to make it valid for the whole page and not only current region... this is a more common need to please lot of people :-)