Contract software engineer (+Toptal): โฅ๏ธ all things Typescript, aspiring ๐งโโ๏ธ, recovering cowboy coder, senior yak shaver, bugs are my own.
While theyโre always great to get going with, the deeper I get into a project, the more I start replacing things, reading their source code, and creating workarounds. In the end, there is only the theming, layout, and icon systems.
@googlechrome@ChromiumDev The update seems to reflect how zIndex handling SHOULD work, as far as I have time to tell, but it was a change that resulted in a production bug.
Sounds like solving bugs to discover more bugs ๐ ... which eventually ends, right?... right?
@googlechrome@ChromiumDev
Chrome 119 -> 120 appears to change how zIndexes are handled. An arguably poor zIndex solution where the children had zIndexes set, but a parent did not ended up being split by outside element with another zIndex.
Hey @keepersecurity
Really annoying that your desktop app grabs some really common shortcuts for other tools, and doesn't allow you to just disable the use of shortcuts... I'm trying to code and navigate the browser and have to discover your desktop app is interfering.
If you convert your popular NPM package from CommonJS to ESM, and don't provide fallbacks, then FUCK YOU. There are too many varied situations to be a fucking purist.
#typescript#javascript#NodeJS
Designers: "Let's use a component library!"
Devs: ๐
Designers: "We're going to make a few modifications, but make a design system in Figma!"
Devs: ๐
Designers: "We're going to totally ignore the existing component library and tokens and do what we want!"
Devs: ๐ฑ๐ญ๐ซ