8614db7a32
* feat: use legacy flag chore: reorder challenges fix: linter revert: server change feat: unblock new editor fix: proper order fix: 0-based order fix: broke the order feat: move tribute certification to its own block feat: split the old projects block into 4 fix: put all blocks in order chore: add intro text refactor: use block, not blockName in query fix: project progress indicator * fix: reorder new challenges/certs * fix: reorder legacy challenges * fix: reintroduce legacy certs * feat: add showNewCurriculum flag to env * chore: forgot sample.env * feat: use feature flag for display * fix: rename meta + dirs to match new blocks * fix: add new blocks to help-category-map * fix: update completion-modal for new GQL schema * test: duplicate title/id errors -> warnings * fix: update completion-modal to new GQL schema Mk2 * chore: re-order metas (again) * fix: revert super-block-intro changes The intro needs to show both legacy and new content. We need to decide which pages are created, rather than than what a page shows when rendered. * feat: move upcoming curriculum into own superblock * fix: handle one certification with two superBlocks * fix: remove duplicated intros * fix: remove duplicate projects from /settings * fix: drop 'two' from Responsive Web Design Two * chore: rename slug suffix from two to v2 * feat: control display of new curriculum * feat: control project paths shown on /settings * fix: use new project order for /settings This does mean that /settings will change before the release, but I don't think it's serious. All the projects are there, just not in the legacy order. * fix: claim/show cert button * chore: remove isLegacy Since we have legacy superblocks, we don't currently need individual blocks to be legacy * test: fix utils.test * fix: verifyCanClaim needs certification If Shaun removes the cert claim cards, maybe we can remove this entirely * fix: add hasEditableBoundaries flags where needed * chore: remove isUpcomingChange * chore: v2 -> 22 Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
155 lines
3.4 KiB
Markdown
155 lines
3.4 KiB
Markdown
---
|
|
id: 5d822fd413a79914d39e98e1
|
|
title: Step 25
|
|
challengeType: 0
|
|
dashedName: step-25
|
|
---
|
|
|
|
# --description--
|
|
|
|
That one used the fallback value as well? I see the problem now! The variables you declared in `.bb1` do not cascade to the `.bb2` and `.bb3` sibling elements. That's just how CSS works. Because of this, variables are often declared in the `:root` selector. This is the highest level selector in CSS; putting your variables there will make them usable everywhere. Add the `:root` selector to the top of your stylesheet, and move all your variable declarations there.
|
|
|
|
# --hints--
|
|
|
|
You should declare a `:root` selector at the top of the stylesheet.
|
|
|
|
```js
|
|
assert.exists(new __helpers.CSSHelp(document).getStyle(':root'));
|
|
```
|
|
|
|
You should define `--building-color1` with a value of `#aa80ff` in the `:root` selector.
|
|
|
|
```js
|
|
assert.equal(new __helpers.CSSHelp(document).getStyle(':root')?.getPropertyValue('--building-color1')?.trim(), '#aa80ff');
|
|
```
|
|
|
|
You should define `--building-color2` with a value of `#66cc99` in the `:root` selector.
|
|
|
|
```js
|
|
assert.equal(new __helpers.CSSHelp(document).getStyle(':root')?.getPropertyValue('--building-color2')?.trim(), '#66cc99');
|
|
```
|
|
|
|
You should define `--building-color3` with a value of `#cc6699` in the `:root` selector.
|
|
|
|
```js
|
|
assert.equal(new __helpers.CSSHelp(document).getStyle(':root')?.getPropertyValue('--building-color3')?.trim(), '#cc6699');
|
|
```
|
|
|
|
You should remove the custom property variables from `.bb1`.
|
|
|
|
```js
|
|
assert.isEmpty(new __helpers.CSSHelp(document).getStyle('.bb1')?.getPropertyValue('--building-color1'));
|
|
assert.isEmpty(new __helpers.CSSHelp(document).getStyle('.bb1')?.getPropertyValue('--building-color2'));
|
|
assert.isEmpty(new __helpers.CSSHelp(document).getStyle('.bb1')?.getPropertyValue('--building-color3'));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>freeCodeCamp Skyline Project</title>
|
|
<link href="styles.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
|
|
<body>
|
|
<div class="background-buildings">
|
|
<div></div>
|
|
<div></div>
|
|
<div class="bb1">
|
|
<div class="bb1a"></div>
|
|
<div class="bb1b"></div>
|
|
<div class="bb1c"></div>
|
|
<div class="bb1d"></div>
|
|
</div>
|
|
<div class="bb2"></div>
|
|
<div class="bb3"></div>
|
|
<div></div>
|
|
<div class="bb4"></div>
|
|
<div></div>
|
|
<div></div>
|
|
</div>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
--fcc-editable-region--
|
|
|
|
* {
|
|
border: 1px solid black;
|
|
box-sizing: border-box;
|
|
}
|
|
|
|
body {
|
|
height: 100vh;
|
|
margin: 0;
|
|
overflow: hidden;
|
|
}
|
|
|
|
.background-buildings {
|
|
width: 100%;
|
|
height: 100%;
|
|
display: flex;
|
|
align-items: flex-end;
|
|
justify-content: space-evenly;
|
|
}
|
|
|
|
.bb1 {
|
|
width: 10%;
|
|
height: 70%;
|
|
display: flex;
|
|
flex-direction: column;
|
|
align-items: center;
|
|
--building-color1: #aa80ff;
|
|
--building-color2: #66cc99;
|
|
--building-color3: #cc6699;
|
|
}
|
|
--fcc-editable-region--
|
|
.bb1a {
|
|
width: 70%;
|
|
height: 10%;
|
|
background-color: var(--building-color1);
|
|
}
|
|
|
|
.bb1b {
|
|
width: 80%;
|
|
height: 10%;
|
|
background-color: var(--building-color1);
|
|
}
|
|
|
|
.bb1c {
|
|
width: 90%;
|
|
height: 10%;
|
|
background-color: var(--building-color1);
|
|
}
|
|
|
|
.bb1d {
|
|
width: 100%;
|
|
height: 70%;
|
|
background-color: var(--building-color1);
|
|
}
|
|
|
|
.bb2 {
|
|
width: 10%;
|
|
height: 50%;
|
|
background-color: var(--building-color2, green);
|
|
}
|
|
|
|
.bb3 {
|
|
width: 10%;
|
|
height: 55%;
|
|
background-color: var(--building-color3, pink);
|
|
}
|
|
|
|
.bb4 {
|
|
width: 11%;
|
|
height: 58%;
|
|
}
|
|
|
|
```
|
|
|