mrdisagree.bsky.social
billiards enthusiast; father; that web components guy; Web Components Community Group member; thoughts and opinions are chat gippity’s
162 posts
260 followers
357 following
Regular Contributor
Active Commenter
comment in response to
post
how do js frameworks play into the “manipulated with js” concept where most of the time folks aren’t writing a querySelector with .dataset but are setting the attr value directly via something like local component state?
comment in response to
post
iirc, the only real differences between custom attrs and data- are 1) access in js via .dataset is data- only, 2) non-dashed attr names might possibly conflict with an eventual native attr at some point in the future. i’m not too worried about name conflicts, so i tend toward custom attributes
comment in response to
post
congrats man! looking forward to all the awesome browser work in the future!
comment in response to
post
i expose certain internal dom elements needed for tests and exception configuration. i call them “internal access props”. they return a dom element instead of another primitive. i expect consumers use those because shadow dom spelunking is brittle af.
comment in response to
post
gives a great new meaning to “shadow parts” lul
comment in response to
post
i am a chronic overexplainer tho haha
comment in response to
post
sorry
comment in response to
post
np!
comment in response to
post
developers.google.com/search/docs/...
comment in response to
post
fuckin yikes.
comment in response to
post
unfortunately there’s barely any trustworthy docs about SEO and shadow dom at all. google has a “we flatten shadow roots” page. bing has a “we do that too, but the test tool is broken and doesn’t”
there’s no definitive source for seo anything beyond those pages and some articles by awesome WC folks
comment in response to
post
lol yikes. this is your website, this is your website on AI.
comment in response to
post
ya edge seems to have it but caniuse isn’t updated yet
comment in response to
post
oh that’s dope. so when the autofill switches the bg color the transition starts and never finishes so it stays whatever color you want it. but i want to be able to set that color too haha
comment in response to
post
inside a flexbox wrapper div so the icons and input can’t crash into each other and w me don’t have to overlay the icons with pos:abs. works great except for autofill lol
comment in response to
post
“security” is my only guess. they wanted to make sure it was hard for folks to obfuscate the fact that it was prefilled i guess?
comment in response to
post
yep! that would remove it, but not change it.
trying to build a custom element input with icon buttons “inside” the field with a flexbox container the actual native input is inside of. autofill makes it weird
comment in response to
post
yep, they use !important in the user agent styles so you can’t override it. you have to use a box shadow or whatevs
comment in response to
post
if it was because the company was trying to minimize legal risk of getting sued it doesn’t count :)
comment in response to
post
[object Object]
and social security numbers!
comment in response to
post
maybe we need a new rem that means “relative to user font size”?
uem?
comment in response to
post
Buying Tesla's unwanted loser vehicles is an insane and unjustifiable waste of government funds, and proof that Musk's so-called Department Of Government Efficiency is a way to strip programs that help real people and funnel them into propping up his own obscene failures. IT MUST NOT STAND.
comment in response to
post
my favorite thing to argue about! :)
comment in response to
post
can’t wait for this to hit every css reset ever
comment in response to
post
yep, checks and balances are gone. seems like they were never really there to begin with if it was all based on the honor system
comment in response to
post
as a parent of a six and four year old, where do i sign?
comment in response to
post
they say while…standing around