Closed peterblazejewicz closed 6 years ago
The input
type has better translation from at-input
type into native type:
https://at-ui.github.io/at-ui/#/en/docs/input
I agree with you. I can't use built-in native feature like submit
types of button. This is a nonstandard practice.
I think that at-button
should have a new prop like nativeType
to handle the built-in native type.
I'll fix it today. Thanks for your detailed comment! @peterblazejewicz
Hi, Just wanted to point, the
type
attribute of nativebutton
is a closed list: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#Attributes and has a special meaning, even in a text-based browsers: https://www.cs.bu.edu/teaching/unix/lynx/The
at-button
bindstype
property into nativebutton
property/attr. Hence theat-button
of defult type:translates to:
which seems fine, but is wrong, as default (and presumed) type is a
button
type while the others are custom, library specific domain language terms:becomes
button
with:The
text
is not a correct attribute by specs.The pick of domain specific translation for a native term seems to prevents me from using builtin native feature like using
cancel
orsubmit
types of buttons to use some built-in native behaviours in the browsers.Let me know if you want a help with this,
Thanks!