|
|
|
|
|
|
by memco
2605 days ago
|
|
|
To add to this: - check the contrast accessibility: it seems very poor for read-only fields due to the opacity. Even the default seems low for body text. I think there’s great documentation of customization, but I had a few questions related to design decision: Why data-readonly and not use readobly and other browser native html5 attributes like validation? Why flexbox and not grid? If you’re only targeting latest browsers: this could provide some greater power. Another thing I noticed is that FF is noted as not supporting CSS scrollbsrs, but it is coming: will Luda be updated when it’s available? |
|
|
Thanks for the good questions!
1. The `data-readonly` attribute behaves different from the native readonly attribute, developers may use the native readonly attribute in their own customized components. I don't want developers to get stuck in such situations. That's why the native readonly attribute is not overridden in Luda.
About native HTML validation: Native validation popovers can not be easily customized in all browsers. Maybe some developers still want to validate forms in JS instead of the native HTML validation. It's a choice to developers how to validate forms, Luda does't limit the ways.
2. CSS grid is an awosome feature, I'm sure it will be implemented in future versions. But before version 1.0.0, making Luda stable is the main target.
3. Luda aims to be a modern framework, so any new features will be considered seriously, including CSS scrollbars in Firefox.
At last, the styles of the form components may be changed due to some problems, not only the contrast accessibility.
I'm very happy you look into Luda for details, please keep an eye on future versions if you're interested. Your suggestions are import to me. Thanks!