Radio group error message placement

[cferdinandi]

For radio groups with messageAfterField set to false, grab first item in group instead of last for error field.

Potentially also use field instead of label.

[robsonsobral]

Wow! I was thinking of that!

  <ul>
    <li>
      <input type="checkbox" id="use-terms" required aria-required="true" disabled>
      <label for="use-terms">
        {{ i18n "iReadAndAccepted" }}
        <a href="/termos-de-uso" target="_blank">
          {{ i18n "useTerms" }}
        </a>
      </label>
    </li>
  </ul>

The data-bouncer-target can be really useful in that case, but I think they should have a hidden attribute by default. From MDN:

The hidden global attribute is a Boolean attribute indicating that the element is not yet, or is no longer, relevant. For example, it can be used to hide elements of the page that can't be used until the login process has been completed. Browsers won't render elements with the hidden attribute set.

[robsonsobral]

(I'm not sure this is the right place for my message. I'm sorry. I'm under medication and a little off.)

[cferdinandi]

I'm not sure I understand what you're saying. Do you mean the target location for the error should be hidden? Ideally it's just an empty div since the message is dynamically rendered.

[cferdinandi]

I'm not sure I understand what you're saying. Do you mean the target location for the error should be hidden? Ideally it's just an empty div since the message is dynamically rendered.

[robsonsobral]

I'm sorry, @cferdinandi . I should have opened a new issue. Yes, an empty element should be hidden until became relevant. The plugin need to check if the hidden attribute is present and remove it.

I'm sorry for the mess.

[cferdinandi]

Oh... I disagree with you on this one. There's no benefit to hiding an empty element. There's no content in it. Screen readers won't announce anything for it, and without content, sighted users won't see it.