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>
110 lines
3.0 KiB
Markdown
110 lines
3.0 KiB
Markdown
---
|
|
id: 5ef9b03c81a63668521804d8
|
|
title: Step 36
|
|
challengeType: 0
|
|
dashedName: step-36
|
|
---
|
|
|
|
# --description--
|
|
|
|
The `input` element is allows you several ways to collect data from a web form. Like anchor (`a`) elements, `input` elements are <dfn>self-closing</dfn> and do not need closing tags.
|
|
|
|
Nest an `input` element in the `form` element.
|
|
|
|
# --hints--
|
|
|
|
Your `form` element should have an opening tag and closing tag in the correct order. You may be missing one or both of the required tags, or have them in the wrong order.
|
|
|
|
```js
|
|
const noSpaces = code.replace(/\s/g, '');
|
|
assert(
|
|
document.querySelector('form') &&
|
|
code.match(/<\/form>/g) &&
|
|
noSpaces.indexOf('<form') < noSpaces.indexOf('</form>')
|
|
);
|
|
```
|
|
|
|
Your `form` element's opening tag should only have an `action` attribute. Remove anything else you may have typed in it.
|
|
|
|
```js
|
|
assert([...document.querySelector('form').attributes].length < 2);
|
|
```
|
|
|
|
You should create an input element. Check the syntax.
|
|
|
|
```js
|
|
assert(document.querySelector('input'));
|
|
```
|
|
|
|
Your `input` element should have an opening tag, but not a closing tag.
|
|
|
|
```js
|
|
assert(document.querySelector('input') && !code.match(/<\/input\>/g));
|
|
```
|
|
|
|
Your `input` element should be nested within the `form` element.
|
|
|
|
```js
|
|
assert(document.querySelector('form > input'));
|
|
```
|
|
|
|
Your `form` should only contain the `input` element. Remove any HTML elements or text between the `form` element's tags.
|
|
|
|
```js
|
|
assert(
|
|
$('form')[0].children.length === 1 &&
|
|
$('form')[0].innerText.trim().length === 0
|
|
);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<html>
|
|
<body>
|
|
<h1>CatPhotoApp</h1>
|
|
<main>
|
|
<section>
|
|
<h2>Cat Photos</h2>
|
|
<!-- TODO: Add link to cat photos -->
|
|
<p>Click here to view more <a target="_blank" href="https://freecatphotoapp.com">cat photos</a>.</p>
|
|
<a href="https://freecatphotoapp.com"><img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg" alt="A cute orange cat lying on its back."></a>
|
|
</section>
|
|
<section>
|
|
<h2>Cat Lists</h2>
|
|
<h3>Things cats love:</h3>
|
|
<ul>
|
|
<li>cat nip</li>
|
|
<li>laser pointers</li>
|
|
<li>lasagna</li>
|
|
</ul>
|
|
<figure>
|
|
<img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/lasagna.jpg" alt="A slice of lasagna on a plate.">
|
|
<figcaption>Cats <em>love</em> lasagna.</figcaption>
|
|
</figure>
|
|
<h3>Top 3 things cats hate:</h3>
|
|
<ol>
|
|
<li>flea treatment</li>
|
|
<li>thunder</li>
|
|
<li>other cats</li>
|
|
</ol>
|
|
<figure>
|
|
<img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/cats.jpg" alt="Five cats looking around a field.">
|
|
<figcaption>Cats <strong>hate</strong> other cats.</figcaption>
|
|
</figure>
|
|
</section>
|
|
<section>
|
|
<h2>Cat Form</h2>
|
|
--fcc-editable-region--
|
|
<form action="https://freecatphotoapp.com/submit-cat-photo">
|
|
</form>
|
|
--fcc-editable-region--
|
|
</section>
|
|
</main>
|
|
</body>
|
|
</html>
|
|
```
|
|
|