gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarification of the declaration order overriding (#19046)

Browse Source 
* Clarification of the declaration order overriding

Previous text was talking about an override but it may also confuse readers that the override was done in the order of the listing of class names inside the h1.
I also added an extra case to better clarify the situation.

* Small change mentioning the order of declaration

Missed an order of declaration emphasis on my previous commit, adding it on this one.
This commit is contained in:
Gökhan Gurbetoğlu
2018-10-16 06:23:15 +03:00
committed by Quincy Larson
parent 80eeb06ac0
commit 0bae15e8c3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
curriculum/challenges/english/01-responsive-web-design/basic-css/override-class-declarations-by-styling-id-attributes.english.md
View File

@ -7,7 +7,7 @@ videoUrl: 'https://scrimba.com/c/cRkpDhB'
## Description
<section id='description'>
We just proved that browsers read CSS from top to bottom. That means that, in the event of a conflict, the browser will use whichever CSS declaration came last.
We just proved that browsers read CSS from top to bottom in order of their declaration. That means that, in the event of a conflict, the browser will use whichever CSS declaration came last. Notice that if we even had put <code>blue-text</code> before <code>pink-text</code> in our <code>h1</code> element's classes, it would still look at the declaration order and not the order of their use!
But we're not done yet. There are other ways that you can override CSS. Do you remember id attributes?
Let's override your <code>pink-text</code> and <code>blue-text</code> classes, and make your <code>h1</code> element orange, by giving the <code>h1</code> element an id and then styling that id.
</section>