Full stack web dev.
Studying FP web development approaches, while helping Mission Bit create paths to programming for underserved public school kids.
Previously @ Gradescope.
Full stack web dev.
Studying FP web development approaches, while helping Mission Bit create paths to programming for underserved public school kids.
Previously @ Gradescope.
I think the explanation of A6 is wrong, if I understand your meaning:
if we apply a featured class on a link we lose all the rules from the nav element
Not all of them -- only the properties which appear in both blocks will be overridden. For the example you gave, the link will have text-decoration: none and color: white. You only "lose" the background-color: green entry.
For Q26, you may want to specify that the container isn't flex, etc.
For A19, I'd use SMACSS :P
Not as concise, but:
Removed the
margin-topas letting the parent handle it means.navListcan be reusable.I love SMACSS. Knowing the specificity rules is good, but not needing to is even better.
This is pretty cool, thanks.
I think the explanation of A6 is wrong, if I understand your meaning:
Not all of them -- only the properties which appear in both blocks will be overridden. For the example you gave, the link will have
text-decoration: noneandcolor: white. You only "lose" thebackground-color: greenentry.For Q26, you may want to specify that the container isn't flex, etc.
Thank you I will fix.
I would have expected a little more flex and grid. Looking forward for the second part.
Yes in the next part which is WIP
A1: unvisited? That may be the state, but that’s not a CSS value as far as I know, :link is (for an unvisited link element).
The old LoVe, HAte!
A14 is incorrect. !important has nothing to do with specificity. It's part of the wider cascade.
I will probably have to rephrase it as
can we override inline styles that marked as !important?ThanxThank you for such helpful resource.
For Q32, I think you meant to say
box-sizing: border-boxinstead of.box-sizing:content-boxGood catch. Thank you