codeofarmz.bsky.social
@bsky.app Hi, how come? Pls explain (the post in this screenshot is mine)
@github.com Could you make the tabs on a PR (Conversation | Commits ...) a second sticky toolbar? Would also be wonderful to have View Deployments popover accessible from there when it is stuck. It could replace the red-green lines diff info if you ask me. Thanks.
Look @platform.jetbrains.com, look. This is so freaking useful when rebasing, esp with reordering commits
I wish @webstorm.jetbrains.com could add an Explain or Fix button directly to all the TSxxxx error popups.
@digitaltransient.bsky.social "Tell me what you need from HTML and CSS" Hi, this sounded so inviting :) I need a better way to manage MULTIPLE `position: sticky` elements on a page. Current model is so limited when you work with UI libraries and frameworks.
CSS is such a gem - you can style `mat-tree` with such a firm layout across all nodes! and even share the same layout with a header that is not even enclosed by mat-tree! That's because you can bubble `display: subgrid` up as many levels as you need. I feel so empowered! cc @kevinpowell.co
When using `position: sticky` on an element that needs to be a margin away from a viewport edge/other sticky, I wish there was something like `overflow-y: curtain-bottom|-top` to make scrolled content disappear beneath the curtain edge (which would extend 100vw) cc @bram.us @nerdy.dev
I love the combo of scrollbar-gutter: stable and scrollbar-width. I wish though we also had a function scrollbar-width() that would return the actual px value, so that we can compensate our paddings etc without using guessed values: padding-right: calc(20px + scrollbar-width(thin)) cc @nerdy.dev
@bram.us Just wanted to ask if what we today have to support position:sticky+scroll-state is considered to be final? Is there maybe any initiative to improve support for multiple sticky elements on a page that want to get stacked on top of each other?
@una.im Hi :) Do you think Anchor API could ever work with sticky and fixed? It'd be awesome if it did - a lot of JS could be ditched to solve these common scenarios: codepen.io/codeOfArmz/p...
I wish container queries could have something like: container-scope: with-self Currently they only act downwards. This makes it difficult to style opinionated libs markup where you can't insert any wrappers. 1/n cc @nerdy.dev
I wish container queries could have something like: container-scope: with-self Currently they only act downwards. This makes it difficult to style opinionated libs markup where you can't insert any wrappers. 1/n cc @nerdy.dev
@bram.us Hi, I've come across this: github.com/w3c/csswg-dr... Do you know if there's any drive to have 'level' implemented?
@obsidian.md When you right-click on a folder item, you can create a document that will be placed as a child of this folder. But why not also right-click on a document item to create a sibling document? Currently, when you have a lot of children in an expanded folder, you have to scroll up first.
Optimist: the cup is half full. Pessimist: the cup is half empty. Pragmatist: the cup has a safety overspill margin to hold all its contents in place.
Optimist: the cup is half full. Pessimist: the cup is half empty. Content Designer: is this the right kind of cup? Is the cup in the right place? Is what’s filling the cup best for the audience at this particular time?
@nerdy.dev Trying to handle a button width: auto transition in pure CSS. Could I ask you if this sort of element swapping is suitable for interpolate-size + starting-style transition? or would it have to be handled by view transitions? codepen.io/codeOfArmz/p...
You are up to date.