getrect.dev
45 posts
22 followers
55 following
Regular Contributor
Active Commenter
comment in response to
post
I think it’s whatever the hell those annoying know-it-alls are droning on about in that morning meeting.
comment in response to
post
@layer has been great when I've used it elsewhere, and I'd like to use it at my company. But until toolchains fully support it (they should), it'll be tough to convince developers to spend the time implementing it.
comment in response to
post
Something else in the library was interfering with how that plugin was being run and styles added. Too bad. But I ran out of time to investigate and had to move on to another task.
comment in response to
post
Unfortunately the library we're using handles all the style management, and I couldn't (quickly) find a way to change how it adds everything.
Emotion.js is under the hood. I was able to build a rudimentary plugin to wrap the styles with @layer, but only some appended styles were affected.
comment in response to
post
Hooooooooot modules…
comment in response to
post
I've tried integrating them into our CSS stack, but keep running into blockers.
During my latest attempt, I found the CSS-in-JS solution from our third-party component library is effectively incompatible. I burned a lot of time writing plugin that would wrap its CSS output in a layer to no avail.
comment in response to
post
How about ‘text-wrap: avoid-singles’? Linguistically it’s about as neutral and simple as I could think of.
comment in response to
post
I can’t wait to use modules to tame the hell that is appended style tags in the head.
comment in response to
post
Signals feel like one of those bits of web tech that just fits really well into the platform. I always liked working with observables, but the API is just a little too cumbersome.
comment in response to
post
I've got a personal project written in Angular, and it's so nice coming back to the class paradigm. For a component with state and a lifecycle to handle, it's so much nicer having a structure to work within.
(and also signals are really sweet to work with.)
comment in response to
post
A lot of web developers fell into the "new hotness" camp. If it's the new way to write a component, it *must* be better, right? Right???
I appreciate some terse abstractions in FCs ( like useState). But some FCs are just const soup filled with hooks that would just be so much cleaner as a class.
comment in response to
post
I’ve been using Stylelint for years, and so far it hasn’t given me any trouble. What’s the value add of using ESLint for CSS? Is it just consolidating linting rules into one tool? Or is ESLint in some way more capable?
comment in response to
post
DOOM was a critical piece of software for web developers. I still use it in my workflow.
comment in response to
post
I’m amazed they still have this in stock. It is literally 30 years old. I wonder if they made so many, it’s taken them this long to sell them all.
comment in response to
post
Love this. What a great way to leverage platform functionality to implement this pattern!
comment in response to
post
Will ident() accept the random() function as an argument?
comment in response to
post
1.7143rem works out to 24.0002px. Watch that .0002px difference be benign until some obscure edge case in 6 months!
This is also why it took me a long time to come around to using ems. I remember seeing really weird subpixel rendering weirdness in Chrome c. 2012 due to fractional pixels.
comment in response to
post
Looks like they aren’t made anymore, but you might be able to find a NIB Visible Woman like this one: www.ebay.com/itm/39559591...
comment in response to
post
Yep, we have print styling applying as expected from the print query.
We have some charts on the page in question, and all the layout weirdness could be the SVGs not scaling properly.
I expect we're going to need to set heights & widths all over the place to lock the dimensions down.
comment in response to
post
A colleague and I were looking into gross rendering quirks between charts, grid, flexbox, and overflow.
This is where gray hairs come from.
comment in response to
post
I think most of the examples still work…
comment in response to
post
I've been building a word search generator for mine as well, and it's ended up being way more elaborate than I anticipated, but still fun to build (and a great learning opportunity).
A little disheartening when the first user test was "meh, dad".
comment in response to
post
4. Automated visual regression testing has got to be a thing - can anyone recommend a solution that doesn't add a whole lot of noise to the testing process?
Solutions I've seen in the past seem fiddly and require a paid subscription somewhere.
comment in response to
post
3. If you're adding layer upon layer of flexy divs just to achieve a 2D layout of rows and columns, just write your own CSS grid.
Flexbox is awesome, but understanding its limits and where, when and how to use CSS grid is part of the job. Play a round of code golf and get rid of some extra markup.
comment in response to
post
2. It's a good idea not to style too deep into a shared component, since they're likely to change on you without notice. I'm 100% guilty of doing this.
comment in response to
post
A few takeaways.
1. Be careful updating the markup of shared components. Adding markup can wreck someone else's selectors that expect a particular pattern.
Ideally, you bump your library's major version. But if that isn't feasible, or you're not using a library, make sure to test your use cases.
comment in response to
post
It’s always good to see new articles about animation and different ways people approach it. I’ve never had the need to use onAnimationEnd, so I’m curious to see what you did with it.
comment in response to
post
I’ve only ever needed counters a handful of times, but they can really come in handy for numbering dynamic content.
comment in response to
post
ChatGPT to the rescue.
comment in response to
post
It makes the child component the arbiter of its own styling. All it needs to do is watch for a flag on the parent. And the parent doesn’t need to clutter its own stylesheet with gnarly selectors for its children.
It’s a neat way to decouple the two, but not necessarily the best for all situations.
comment in response to
post
Once I got it working, it felt a little roundabout and verbose; why go through the trouble of setting up a flag and wire the query in the child? A basic selector in the parent could handle this easily (and quickly).
But… I still kinda liked the pattern.
comment in response to
post
But… but… my agglomerated data! How will I know I did things??