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
Another issue is what to do if there are multiple <input /> elements (like dual input Range Sliders because you can't have multiple ids on a page
Another issue, that's been somewhat hastily solved by the hasChildLabel prop on EuiFormRow, is with wrapped <input /> elements that already have an applied label
And, the impetus for making this issue, for the case of a searchableEuiSelectable, the <input /> needs the passed in id but also an associated element (a ul in this case) needs a reverse aria-describedby set to the label's id.
@chandlerprall suggested that this might be solved by somehow using React's context to do all this...
EuiFormRow passes down the
idaninputelement should take on to wire up EuiFormRow's<label>correctly.But there are several cases where this breaks down:
idnever makes it to the<input /><input />elements (like dual input Range Sliders because you can't have multiple ids on a pagehasChildLabelprop on EuiFormRow, is with wrapped<input />elements that already have an applied labelsearchableEuiSelectable, the<input />needs the passed inidbut also an associated element (aulin this case) needs a reversearia-describedbyset to thelabel'sid.@chandlerprall suggested that this might be solved by somehow using React's context to do all this...
Kind of related to #2493