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>
85 lines
1.4 KiB
Markdown
85 lines
1.4 KiB
Markdown
---
|
|
id: 60a3e3396c7b40068ad69981
|
|
title: Step 24
|
|
challengeType: 0
|
|
dashedName: step-24
|
|
---
|
|
|
|
# --description--
|
|
|
|
Create a new CSS rule using the `.two` selector and set its `width` to 475 pixels.
|
|
|
|
# --hints--
|
|
|
|
You should have a `.two` selector.
|
|
|
|
```js
|
|
const hasTwo = new __helpers.CSSHelp(document).getStyle('.two');
|
|
assert(hasTwo);
|
|
```
|
|
|
|
You should set the `width` property to `475px`.
|
|
|
|
```js
|
|
const hasWidth = new __helpers.CSSHelp(document).getCSSRules().some(x => x.style.width === '475px');
|
|
assert(hasWidth);
|
|
```
|
|
|
|
Your `.two` element should have a `width` value of `475px`.
|
|
|
|
```js
|
|
const twoWidth = new __helpers.CSSHelp(document).getStyle('.two')?.getPropertyValue('width');
|
|
assert(twoWidth === '475px');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```css
|
|
.canvas {
|
|
width: 500px;
|
|
height: 600px;
|
|
background-color: #4d0f00;
|
|
overflow: hidden;
|
|
}
|
|
|
|
.frame {
|
|
border: 50px solid black;
|
|
width: 500px;
|
|
padding: 50px;
|
|
margin: 20px auto;
|
|
}
|
|
|
|
.one {
|
|
width: 425px;
|
|
height: 150px;
|
|
background-color: #efb762;
|
|
margin: 20px auto;
|
|
}
|
|
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
|
|
```
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<title>Rothko</title>
|
|
<link href="./styles.css" rel="stylesheet">
|
|
</head>
|
|
<body>
|
|
<div class="frame">
|
|
<div class="canvas">
|
|
<div class="one"></div>
|
|
<div class="two"></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|
|
```
|