@codeofarmz.bsky.social
New features, new layouts...?
Is it going to be easy for the user to tamper with such a flag?
Is it going to be easy for the user to tamper with such a flag?
December 6, 2025 at 2:53 PM
New features, new layouts...?
Is it going to be easy for the user to tamper with such a flag?
Is it going to be easy for the user to tamper with such a flag?
Host with the most!
November 23, 2025 at 5:43 PM
Host with the most!
So would that be something like:
<textarea id="my-text-area"></textarea>
<input type="emoji" for="my-text-area">
and would insert emoji at caret?
<textarea id="my-text-area"></textarea>
<input type="emoji" for="my-text-area">
and would insert emoji at caret?
November 23, 2025 at 4:56 PM
So would that be something like:
<textarea id="my-text-area"></textarea>
<input type="emoji" for="my-text-area">
and would insert emoji at caret?
<textarea id="my-text-area"></textarea>
<input type="emoji" for="my-text-area">
and would insert emoji at caret?
Nay. IMO accessing emojis should be a subfeature of <input type="text"> or <textarea> or [contenteditable].
November 15, 2025 at 4:29 PM
Nay. IMO accessing emojis should be a subfeature of <input type="text"> or <textarea> or [contenteditable].
The biggest problem is having to use fixed/pre-computed ("magic") positions instead of being able to refer to an edge. The anchor() positioning doesn't work here. With one sticky, not big of a problem, mutliple - starts to be a nightmare.
The link: github.com/w3c/csswg-dr...
The link: github.com/w3c/csswg-dr...
[css-position] ‘Sticky’ behavior is too limited as position scheme created from the elements nearest block level ancestor & margins · Issue #2496 · w3c/csswg-drafts
https://drafts.csswg.org/css-position-3/#sticky-pos TLDR Should "sticky" be defined by its own property that sets edge and distances within a containing block defined by the elements "offset parent...
github.com
November 8, 2025 at 10:51 AM
The biggest problem is having to use fixed/pre-computed ("magic") positions instead of being able to refer to an edge. The anchor() positioning doesn't work here. With one sticky, not big of a problem, mutliple - starts to be a nightmare.
The link: github.com/w3c/csswg-dr...
The link: github.com/w3c/csswg-dr...
More capabilities for multiple "position: sticky".
There is one github ticket but kinda dead.
There is one github ticket but kinda dead.
November 6, 2025 at 3:46 PM
More capabilities for multiple "position: sticky".
There is one github ticket but kinda dead.
There is one github ticket but kinda dead.
I would love a post-mortem of some Angular Material components or CDK tools, explain decisions made...
October 18, 2025 at 9:46 PM
I would love a post-mortem of some Angular Material components or CDK tools, explain decisions made...
Oh thank you for enlightening me about the scope.
October 18, 2025 at 9:45 AM
Oh thank you for enlightening me about the scope.
The multiple stickies + anchor() function is what I'm after.
(but yes, I could still be doing it wrong)
codepen.io/codeOfArmz/p...
(but yes, I could still be doing it wrong)
codepen.io/codeOfArmz/p...
October 18, 2025 at 8:38 AM
The multiple stickies + anchor() function is what I'm after.
(but yes, I could still be doing it wrong)
codepen.io/codeOfArmz/p...
(but yes, I could still be doing it wrong)
codepen.io/codeOfArmz/p...
Yes I tried it.
October 17, 2025 at 8:11 PM
Yes I tried it.
I wish anchor positioning could query `position: sticky` elements for their edges. This would put end to using magic numbers.
October 17, 2025 at 5:38 PM
I wish anchor positioning could query `position: sticky` elements for their edges. This would put end to using magic numbers.
Oh, this one. I already commented on it. But since there's not much traction, I thought maybe I should try a different one :)
Thanks :)
Thanks :)
October 16, 2025 at 4:36 PM
Oh, this one. I already commented on it. But since there's not much traction, I thought maybe I should try a different one :)
Thanks :)
Thanks :)
Is there any ongoing initiative regarding enhancing of `position: sticky` capabilities? I find the current state of affairs very limiting, and would like to follow some conversations or contribute with use cases.
October 16, 2025 at 4:28 PM
Is there any ongoing initiative regarding enhancing of `position: sticky` capabilities? I find the current state of affairs very limiting, and would like to follow some conversations or contribute with use cases.
Thank you. Yes, of course, overlaying like this would disable swiping, but I like this ::scroll-button pseudo anyway, so many choices :)
October 15, 2025 at 6:11 PM
Thank you. Yes, of course, overlaying like this would disable swiping, but I like this ::scroll-button pseudo anyway, so many choices :)
Is it possible to overlay a carousel with 2 transparent halves that would link to prev/next? I mean pure css of course.
October 14, 2025 at 6:19 PM
Is it possible to overlay a carousel with 2 transparent halves that would link to prev/next? I mean pure css of course.
There is a special place in hell for the people who limit your time on stage.
It's Carnegie Hell ;-)
It's Carnegie Hell ;-)
October 13, 2025 at 7:06 PM
There is a special place in hell for the people who limit your time on stage.
It's Carnegie Hell ;-)
It's Carnegie Hell ;-)
This reminds me to submit a ticket about "Surround With" for WebStorm, because it requires so much post-polishing :)
October 11, 2025 at 6:13 PM
This reminds me to submit a ticket about "Surround With" for WebStorm, because it requires so much post-polishing :)
I like color-mix, but I wish it would look into the first color's transparency first, before assuming 50%-50%
October 7, 2025 at 8:10 PM
I like color-mix, but I wish it would look into the first color's transparency first, before assuming 50%-50%
Version 140.0.7339.208 (Official Build) (arm64)
Crashing reproducibly with scroll-target-group (Angular CLI app)
But I also managed to crash scroll-marker-group once from chrome.dev/carousel/ver...
Will try to use chrom/crashes as suggested by @bram.us
Crashing reproducibly with scroll-target-group (Angular CLI app)
But I also managed to crash scroll-marker-group once from chrome.dev/carousel/ver...
Will try to use chrom/crashes as suggested by @bram.us
September 29, 2025 at 5:26 PM
Version 140.0.7339.208 (Official Build) (arm64)
Crashing reproducibly with scroll-target-group (Angular CLI app)
But I also managed to crash scroll-marker-group once from chrome.dev/carousel/ver...
Will try to use chrom/crashes as suggested by @bram.us
Crashing reproducibly with scroll-target-group (Angular CLI app)
But I also managed to crash scroll-marker-group once from chrome.dev/carousel/ver...
Will try to use chrom/crashes as suggested by @bram.us
Yes, you can cook a CSS-only egg with that :)
September 25, 2025 at 4:18 PM
Yes, you can cook a CSS-only egg with that :)
"Accept all"
September 24, 2025 at 6:36 PM
"Accept all"
Yes, they are powerful, but I find the options menu and code selection prerequisites a bit overwhelming. I usually prefer doing it all by myself.
The new Refactor palette doesn't seem to help much either.
The new Refactor palette doesn't seem to help much either.
September 23, 2025 at 4:56 PM
Yes, they are powerful, but I find the options menu and code selection prerequisites a bit overwhelming. I usually prefer doing it all by myself.
The new Refactor palette doesn't seem to help much either.
The new Refactor palette doesn't seem to help much either.