@daboigbae@saltnburnem I prefer the left version because it gives better feedback to the user on what to expect.
Of course there are packages which create skeletons but I in my opinion not worth it to inject an unnecessary dependency for such an easy feature. Just create HTML and style it via CSS.
The CSS cascade and its inheritance is not to be seen as a bug, one needs to fight by creating hashed class names or putting CSS into JS files, but a core feature of the language one needs to learn to understand and cherish.
Note to myself: JavaScript's intersection observer API sometimes doesn't work as expected when setting the intersection root element's overflow to something else than visible.
π₯π¦ #Firefox is finally supporting container queries according to https://t.co/4bXQDz1la1. I think it's time for me to slowly migrate to use these. Very good tutorial video by @jherr on youtube: https://t.co/qlkmgRBJ1n
Learning about the usage of emojis within #HTML, #CSS and #JavaScript files. https://t.co/d6c1gFJzEd
I think this interpretation of the cat emoji recaps the respective company's philosophy pretty decently.
@parasight@GatsbyJS It could be indeed a bit more clear. But isn't this maybe indicating that the error container isn't wrapped correct in your React code? Maybe fiddling around with parent and child elements could solve this? Or is this exclusively related to your node_modules?
Very interesting article by @brucel explaining the W3C's versioned specification and why using the <h1> element across your document for a generic heading was never really working. I also fell for this trap in the past. ^___^
https://t.co/PRF3SGI4M7