Isn't CSS always "executed" from top to bottom? In that case the last CSS rule for an item aplies. This could be diffrent if you where more specific with a selector or use !important .
I removed duplicate entries. I am just reporting a bug this time. 
Dilip I'm sorry, but what exactly is the bug here? CSS instructions will overwrite previous entries, if one of these three conditions are met:
The selector has a higher specificity, e.g. .class is overwritten by body .class
Those were duplicate entries
You're using the !important modifier
No, not in use
The selector appears twice or has an equal weight, in that case the one that appears last will win
Does that mean, in duplicate entries, last one will win ? Only hex codes are different.
Does that mean, in duplicate entries, last one will win ? Only hex codes are different.
Exactly, that is how CSS works.
https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity provides quite a good explanation on CSS selectors and how they are evaluated. The section on Tree proximity ignorance is also interesting, as this is quite often misunderstood.
Don’t have an account yet? Register yourself now and be a part of our community!
