Karol
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
...also thank you kindly for all the input, this was my first post on this channel and I'm glad I tried to post here 🙂
48 replies
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
Didn't even know this existed, but solves my problem 😄
this is way cleaner than adding disabled to every single input.
And is it OK if I put my custom submit Button inside it as well from semantic point of view?
As the name indicates, button is not really a field...
48 replies
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
yes, I know, but there isn't much of an issue here, just need some advice or recommendation for clean solution.
My code is behaving as expected for now. I just figured I might ask here first instead of wasting time to implement some
not so clean solution 🙂
48 replies
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
48 replies
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
one sec, I'll try to draw it so that will explain better.
48 replies
KPCKevin Powell - Community
•Created by Karol on 2/19/2025 in #front-end
Form status message
but that would shrink the outside container. The size isn't fixed now, it is based on the inputs and button size.
48 replies
KPCKevin Powell - Community
•Created by γιαννη on 2/19/2025 in #front-end
Positioning Issues
Why would you force going with flex?
You said you would like to keep it simple but going with flex on your 'fareContainer' div is actually opposite, basically what @dys 🐙 said 🙂
4 replies