You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, it's difficult to confirm the presence of certain states on form groups. For instance, consider an email field with an error. Today, we get this:
Its hard to confirm the presence of the help-block with other inputs in the same form, because the outer form-group has no identifiable information on it. This requires a selector like this to ensure it's the help-block associated with the email-address input:
$('input#Email-Address ~.help-block')
It would be much easier if the outer form-group had an identifiable class or id to select. Then it would just be something like:
Even a bigger concern if you consider i18n. Label is mostly translated, which is used for input id. So you have to deal with translation issues just to identify your form fields in acceptance tests.
You could pass a class name in like this to use in your acceptance tests:
Right now, it's difficult to confirm the presence of certain states on form groups. For instance, consider an email field with an error. Today, we get this:
Its hard to confirm the presence of the
help-block
with other inputs in the same form, because the outerform-group
has no identifiable information on it. This requires a selector like this to ensure it's thehelp-block
associated with theemail-address
input:It would be much easier if the outer
form-group
had an identifiableclass
orid
to select. Then it would just be something like:without using the more uncommonly used sibling selector.
This should be implemented on all components, including
checkbox
since, today, they're not uniquely identifiable.The text was updated successfully, but these errors were encountered: