clevermissfox
clevermissfox
Explore posts from servers
KPCKevin Powell - CommunityCDCloudflare Developers
PostsComments
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
maybe inert attribute on form ?
37 replies
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
I was picturing generic for all elements but didn’t really think about it too long. Something like 
form.querySelectorAll(“*:not(label)”).forEach(input => {//etc} 
form.querySelectorAll(“*:not(label)”).forEach(input => {//etc}
toggling the attr on the fieldset works too. I suppose it is a group of related content so it’s not entirely unsemantic but not necessarily semantic either 😆 Anyways OP you’ve got a few options now ✨
37 replies
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
Aha I see what you’re saying now
37 replies
KPCKevin Powell - Community
Created by Harry05 on 2/17/2025 in #ui-ux
Start make web App from 0%
user journey vs user flow
7 replies
KPCKevin Powell - Community
Created by Harry05 on 2/17/2025 in #ui-ux
Start make web App from 0%
https://creately.com/static/assets/guides/user-flow-diagram/e-commerce-order-process-flowchart.webp
7 replies
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
What checkbox? Mandatory by law but doesn’t exist in the form?🤔
37 replies
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
if you add the checkbox that's mandatory by law, and that doesnt exist in the form, then you need to remember to modify the javascript too
37 replies
KPCKevin Powell - Community
Created by γιαννη on 2/19/2025 in #front-end
Positioning Issues
Is image one what you’re aiming for ? (Image one being with the grey “go back” button and yellow/white borders on the fare amounts ?
4 replies
KPCKevin Powell - Community
Created by Karol on 2/19/2025 in #front-end
Form status message
Loop through and add a disabled attribute to all the inputs. If it made sense for semantics you could apply one disabled attribute to <fieldset> and that would disable all inputs inside (just mentioning for future reference; a fieldset doesn’t look appropriate for using in this form ) Use pointer events: none
37 replies
KPCKevin Powell - Community
Created by omar_ab(@om4rAb) on 2/18/2025 in #front-end
Having hard time making Image fits the height | not easy as you think
Ah I see 😆
85 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
Their hallucinations are wild !! And even when it’s giving you right answers , still makes plenty of errors. Fed it some code to comment for me and it gave it back with comments but also changed one character in my selector which broke everything. It’s so unreliable that it’s scary when people use it but don’t know how to check the output; they get stuck as soon as there’s one error or ridiculous hallucination. More trouble than it’s worth for beginners- their time would be better spent just learning whatever they’re trying for a lot of the simple stuff
24 replies
KPCKevin Powell - Community
Created by denartha10 on 2/14/2025 in #ui-ux
UI looks zoomed in
Yea I could def see it being used in the wrong way but there’s gotta be some use cases … or maybe the use cases are so few and that’s why no one uses it😆
31 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
AI says yes - but would def have to test to check 
@supports at-rule(@layer) {
  /* Code for browsers that support @layer */
}

@supports not at-rule(@layer) {
  /* Fallback for browsers without @layer support */
}
@supports at-rule(@layer) {
  /* Code for browsers that support @layer */
}

@supports not at-rule(@layer) {
  /* Fallback for browsers without @layer support */
}
24 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
I’m not sure 🤔
24 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
Although if you’re importing your stylesheets at least you wouldn’t have to write your styles twice
24 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
And not worth using an @supports imo
24 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
I misspoke - it’s baseline to the point I use in my demos and codepens as most people looking at codePen will be on a modern browser. Since it’s not a progressive enhancement and will break everything if the browser doesn’t recognize I think it’ll be a bit until it’s implemented more eg Once it’s being used more frequently in production sites I should say
24 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
Same - I avoid it like the plague so that I have the silver bullet in case I need it and don’t raise specificity for no reason; when I need it, is usually to override framework or library’s selectors. Once @layer is supported that’s gonna make it even less common
24 replies
KPCKevin Powell - Community
Created by denartha10 on 2/14/2025 in #ui-ux
UI looks zoomed in
Gotcha , thanks! Very interesting I love coming across new/old properties
31 replies
KPCKevin Powell - Community
Created by Tok124 (CSS Nerd) on 2/18/2025 in #front-end
view-transition exclude navbar issue
Yay glad it works ! Using ID selectors for view transition name might be one of the few times I’ll use IDs in css - since IDs and view transition names are unique to each page sounds like a match ! Then we can ensure each has its own name.
24 replies