Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

completed exercises 2 and 3 #61

Open
wants to merge 24 commits into
base: master
Choose a base branch
from
Open

Conversation

zenebu
Copy link

@zenebu zenebu commented Feb 26, 2019

No description provided.

Copy link
Member

@tekul tekul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work Zenebu. There seems to be some stuff missing though? For example exercises 2, 3, 7 and 8? And exercises after 23? If you haven't finished then it's a good idea to say that when opening your PR. It just says "completed exercises 2 and 3".

10 error missing script: week
11 error If you need help, you may report this error at:
11 error <https://github.com/npm/npm/issues>
12 verbose exit [ 1, true ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Be careful to review your changes before committing them :). Use git status and git diff to check what's changed and what you are adding, and don't use the commands git add . or git commit -am (even if you see instructions somewhere that say to do that 🙂 ).

</div>
</div>
</main>
</body>
</html>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only thing you're meant to do for exercise 1 is add a time value to the HTML. Exercises 2 and 3 should be changes in other files (you don't seem to have done those?).


#first-message {
background-color: red;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

font-size: 0.9rem;
}
.message_content {
opacity: 1;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you check whether this works? Always run the code (or view the web page here) and make sure the changes you make have the intended effect. Look up what opacity does and try to experiment with different values.

@@ -11,7 +11,9 @@
<body>
<div class="site-wrapper">
<main>
<p>Delete this line and add your form.</p>
<form action="https://www.google.com/search" method="Git">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're confusing GET with Git here 🙂

@@ -37,8 +37,12 @@ <h1 class="shopping-basket__title">Your Shopping Basket</h1>
<div class="checkout">
<h2 class="checkout__title">Checkout</h2>
<form method="GET" id="checkout-form" class="checkout__form">
<!-- Add the form fields here -->

<label> for="customer-name">customer-name</label>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text values for the labels should be normal text the user will see on screen, so something like "Name" rather than "customer-name", and "Email" rather than "customer-email".

<input id="customer-name" type="text" name="customer-name">
<label for="email">customer-email</label>
<input id="email" type="email" name="customer-email">
<label for="tel">customer-phone</label>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The for attribute must match the id attribute of the element it corresponds to. The id isn't tel in this case.

<form>
<label>Add Your Message</label>
<textarea> comment </textarea>
<button>Send Comment</button>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remember the label must always be explicitly matched to another element (even if it seems obvious to you what it is for here, because there is only one input field. We saw two ways to do this, you can use either.

<fieldset>
<legend>dietry requirments</legend>
<label>
<input type="checkbox" name="yumy food" value="ha" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Watch out for typos. You have two fields here, one called yumy food and one called yummy food.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tanks for your feedback and recommendation.i will finish the rest of exercises.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants