Why isn't this CSS doing anything?

[@jay_tuckey]

Thanks for these vids, they are amazing! So helpful, and such clear description of what's going on!

[@rgilmour70]

This is a fantastic feature!

[@eveningcoder8666]

Why are your videos always so helpful?

[@slavenDj]

Wow! 😲 I don't see that coming. Thank You so much.

[@beardcat]

You are amazing. Thank you for all these videos :)

[@sankalp_choudhary]

Great

[@patrickc.6183]

Really great! I love this feature of Firefox :).

[@imranali-kn6mv]

Nice explanation...

[@SigmaticDev]

I see you House of Leaves.... 👀 Not only is Miriam a great CSS teacher but she's got good taste too

[@mesalesme7501]

why is it some css only changes things if its written into the html (not in a separate style sheet)

[@oceaneyes6118]

hover ,before and after don't work ..what should I do ??

[@authentickenyan6284]

Really useful ! Thank you for this tip !

[@Chaudharys1]

how to inspect code in sublime text

[@imranali-kn6mv]

Please help me out for this I have one problem for page-break-inside property is not working in firefox and in rest of the other browsers it is working fine but only problem in firefox .I am using -moz- perefix for this property but it is showing grey color can you upload a video for the same problem or you can tell me here. Thanks in advance

[@ih8tusernam3s]

Thanks for the videos.

[@aram5642]

How I wish FF could also help in discovering why a page gets a mysterious (vertical or horizontal) scrollbar in cases where it is not expected... Not sure how I would like it to work, but I would like it to read my emotions when it happens :) Currently it display an element tag [scroll] "This element has scrollable overflow" but no help

[@Ana-fj6nv]

Great video! I see that mistakes are shown just in demo.css, the changes that you do live, but is there a way for this function to identify errors that are already in the whole code (not just the part edited at the moment) ?

[@amipost]

That's Great! THANK YOU!

[@pankajpanda]

you solved my issue. Thank very much

[@freezeone9666]

why this channel not active

[@ManvendraSK]

I'm learning CSS, and Firefox has made it much easier to visualize clips, shapes, grids, and flexboxes. Really good work than Chrome dev tools. Oh yes, you got icons too on the dev tools panels, something Chrome doesn't have either. Firefox rocks!! ✌🏼

[@fi-losopher]

Hey I'm just getting started and I'm facing a problem;my style attributes like background color and images are not showing up in my firefox webpage, it's showing html just fine but css is not showing up. Please help

[@Vaeshkar]

Thank you.

[@MeAdhir]

Awesome, superior compare to Chrome Dev tool.

[@henrikostman4474]

Sooo long coming. Best since sliced bread.

[@vlad1655]

Lol, ofc you have an example with your face in there. 🤣

[@DavidsonPaulo]

*(downloading Firefox...)*

[@davidamadore]

This is very useful. But there are so many reasons why a CSS rule might fail to do anything (it could have the wrong syntax, it could fail to match, it could be overridden by another rule, the stylesheet could fail to load or fail to be included properly, etc.), I think it's a bit of an oversell to say this will always tell us the reason: it will sometimes explain the problem, and often provide a helpful insight, but it's not a panacea either.

[@etiennedud]

Well as the engine is responsable for the activation of the css, it can tell you why it did not took that part of the css sheet.

[@kawaiihikari0]

Is this a dude 😂 💀

[@1conscience0dimension]

wtf is this????

[@ch3zburg4r]

ywnbaw

[@halo2bullseye922]

Thanks for the video!