codeofarmz.bsky.social

codeofarmz.bsky.social

@codeofarmz.bsky.social

10 followers41 following241 posts

@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.

Of all the recent CSS features I've been mostly using scroll-state. To get it working can be tricky because container queries only act on descendants, so it can require specific HTML structure. While :after :before are also descendants, forcing them behind (as for toggling horizontal shades)

can be tough as well, if impossible. In fact using z-index to control things can often destroy the solution, `isolation: isolate` - I didn't find it useful here. But I've been much more successful with scroll-state than with starting-style.

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

View full thread

With `container-scope: with-self` I could actually style the element that gets stuck - quite a common scenario, I'd say. Maybe with-self could only apply to scroll-state, IDK, but I feel like this is a missing piece of the API. I'd love to be proved wrong!

For example, trying to add box-shadow on mat-table when it is scrolled: I need to query "stuck: top" on mat-header-row - but with the descendants-only scope I'm only able to style its children, ie. individual mat-header-cell. This produces unwanted artifacts when using large box-shadow values 2/n

Looks like the new year resolutions kick in mostly in the area of newsletter sendouts. Been getting a lot of emails last days from companies and individuals that I forgot even existed. They resurrected from dust and oblivion. "1. We need to do better with our internet presence in 2025."

@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.

Sarah Winters@escmum.bsky.social

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?

You are up to date.