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
The <fast-text-area> lacks some attributes present on the native component.
馃捇 Repro or Code Sample
Missing attributes (based on MDN): autocapitalize (nonstandard), dirname, autocomplete (nonstandard), autocorrect (nonstandard) and wrap.
馃 Expected Behavior
autocapitalize while nonstandard, might be useful and should be set on the underlying textarea in the template.
dirname doesn't work, but is quite a niche attribute and has an unusual behavior that might be tricky to emulate.
autocomplete is nonstandard, doesn't work in any browser AFAIK and can be safely ignored.
autocorrect while nonstandard, might be useful but is not yet defined (PR stuck here) and can continue to be ignored atm.
wrap should work when set on the underlying textarea in the template but currently doesn't?
馃拋 Possible Solution
autocomplete is useless and autocapitalize is just about updating the component's template, so those are easy ones.
It'd be nice to get wrap to work, maybe autocorrect too and dirname if the implementation is not too complex.
The text was updated successfully, but these errors were encountered:
馃悰 Bug Report
The
<fast-text-area>
lacks some attributes present on the native component.馃捇 Repro or Code Sample
Missing attributes (based on MDN):
autocapitalize
(nonstandard),dirname
,autocomplete
(nonstandard),autocorrect
(nonstandard) andwrap
.馃 Expected Behavior
autocapitalize
while nonstandard, might be useful and should be set on the underlying textarea in the template.dirname
doesn't work, but is quite a niche attribute and has an unusual behavior that might be tricky to emulate.autocomplete
is nonstandard, doesn't work in any browser AFAIK and can be safely ignored.autocorrect
while nonstandard, might be useful but is not yet defined (PR stuck here) and can continue to be ignored atm.wrap
should work when set on the underlying textarea in the template but currently doesn't?馃拋 Possible Solution
autocomplete
is useless andautocapitalize
is just about updating the component's template, so those are easy ones.It'd be nice to get
wrap
to work, maybeautocorrect
too anddirname
if the implementation is not too complex.The text was updated successfully, but these errors were encountered: