Making Your CSS Fail Excellently - 7/7 Resilient CSS
HTML-код
- Опубликовано: 5 фев 2025
- In the last of the Resilient CSS series, Jen explains when you can't use a newer CSS property. It all depends on whether or not that property will fail well.
Thanks to Jeremy Keith for this idea of understanding if something “fails well” being key in deciding whether or not it's a good idea to use it. He has a great talk about this, Evaluating Technology: • Evaluating Technology ...
it is shocking that these videos do not have thousands of likes. These are just the best!
Great content and very well detailed! Looking forward for more series like these. This channel needs more visibility!! Nice job!
Such a great series! Thank you!
Great series! Everything to the point. Thanks.
Thank you for this series. I've learned quite lot.
I love this series! Thank you so much!!
Great video, again. This was a very helpful series of episodes! I was also wondering if you could do a video on responsive navigation with CSS Grid in the future. That'd be awesome!
I have learned so much from your videos! I can't thank you enough.
As an aspiring web developer who hopes to work with Mozilla in the future, I find you to be very inspirational. This was a great mini-series, though it left me questioning how I can go about creating a website bottom up with these principles. I've heard much on mobile first, responsive design, semantic structure, and progressive enhancement however very few videos have explained such things as elegantly.
Another mini-series tutorial on building a website incorporating these principles in a fail safe manner would be enlightening. Regardless, great videos!
I opened all your videos from Resilient CSS series to give them a thumbs up, and noticed that you start every video with a "So".
Thank you for making these videos! I learned a bunch of new stuff I can now use to make my CSS (fail) better. :)
Thank you so much for what you're doing ma'am. As a newbie in frontend development I have gotten better at implementing CSS like a pro and this has helped my confidence alot. Please can you do a video about "box-shadow"? This is one of some areas I still struggle to grasp. As a great teacher I believe my problems will be solved if you can shed some light on it. Thanks
A great series. I've learnt a lot about fallback.
Great series, I'll definitely recommend this.
Great resource! Kepp the recordings coming :)
Bonjour,
Merci beaucoup pour cette série qui était très intéressante et très instructive.
Ciao :)
I must say that I am somewhat disappointed, I got to the final video of this list hoping to find another explosion like the third video and this did not happen, anyway I think I learned a lot. Thank you very much for these videos!
Thank you for this series :)
Is there a browser testing tool, where you can see how the code runs on all 3 browsers side by side?
Love the video series! ... what is your opinion on how flexbox fails (particularly in IE)? I'm leaning towards adopting a newer framework (BS4, Foundations, Bulma to name a few), but I'm worried about flexbox bugs with IE11. One of the tricker bugs that I've run into more often with IE flexbox was the flex-direction: column issue with children sizing.
thank you for this series
what is the result of the css overrides on paint performance? Does it affect it at all? Or the browser decides what to render before it goes to the GPU?
U r Awesome ma'am becouse of u i started using css grid and i feel great, i love it but how can i go deep inside css grid, i want to learn it to advanced level, pls suggest some free resources thanks......
Whilst this is a great series, and the sentiment is commendable, it doesn't deal with the elephant in the room: the time incurred to QA a site on legacy browsers. For a large company which can afford to outsource QA or has a good sized QA department this might not be a problem, but for smaller shops, startups and independent developers, spending that kind of time checking sites in a multitude of browsers is simply not practical. In my experience, even if a project starts out intending to support a good selection of legacy browsers, this support is often dropped when time gets short and there isn't enough capacity for testing and fixing bugs. Obviously for the low-hanging fruit used in these examples this isn't much of a problem, but when you start applying these techniques to mission critical elements like layout and navigation this becomes far more of an issue and need far more thorough testing. It's interesting because this is exactly the same problem I've seen time and again with accessibility. Even if a developer or team have the knowledge to implement properly, the difficulties of testing and the realities of hitting deadlines mean this often falls by the wayside. The one thing most developers lack is the luxury of time.