Birmingham | 26-ITP-Jan | Mohammed Omer | Sprint 2 | Form-Control#1184
Birmingham | 26-ITP-Jan | Mohammed Omer | Sprint 2 | Form-Control#1184mo-omer wants to merge 6 commits intoCodeYourFuture:mainfrom
Conversation
✅ Deploy Preview for cyf-onboarding-module ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Form-Controls/index.html
Outdated
| </main> | ||
|
|
||
| <footer> | ||
| <p>Website Dedicated To T-shirt Sale</p> |
There was a problem hiding this comment.
We had slightly different requirements for the content of this footer. Let's check the edited files again and address it.
| </p> | ||
| </section> | ||
|
|
||
| <!-- Colour Selection --> |
There was a problem hiding this comment.
Let's look into the colour selection a bit more, specifically the options. Do you see anything that might look off and not fulfil the requirements?
Form-Controls/index.html
Outdated
| Red | ||
| </label> | ||
|
|
||
| <p> |
There was a problem hiding this comment.
We are wrapping radio buttons into paragraphs, which might be a better fit for text. Can you find a more appropriate tag to wrap them instead?
Form-Controls/index.html
Outdated
| </div> | ||
|
|
||
| <label> | ||
| <input type="radio" name="colour" value="red" required /> |
There was a problem hiding this comment.
This radio button was declared in a slightly different way than others, it's not getting the CSS changes and doesn't fulfil the original requirements to be associated with the input. How can we improve it?
|
Let's also improve the |
cjyuan
left a comment
There was a problem hiding this comment.
- According to https://validator.w3.org/, there is one warning. Can you address it?
Form-Controls/index.html
Outdated
| <div> | ||
| <input type="radio" id="red" name="colour" value="red" required /> | ||
| <label for="red">Red</label> | ||
| </div> | ||
|
|
||
|
|
||
| <div> | ||
| <input type="radio" id="black" name="colour" value="black" required /> | ||
| <label for="black">Black</label> | ||
| </div> |
There was a problem hiding this comment.
This implementation does not quite meet the requirements specified in README.md. Please check the spec to find out what you missed.
There was a problem hiding this comment.
added 3rd colour section to meet README requirement
<div>
<input type="radio" id="blue" name="colour" value="blue" required />
<label for="blue">Blue</label>
</div>
Form-Controls/index.html
Outdated
| <input type="radio" id="xs" name="size" value="XS" required /> | ||
| <label for="xs">XS</label> |
There was a problem hiding this comment.
Could also consider wrapping the radio button input inside the label tag as:
<labe>
<input type="radio" name="size" value="XS" required />
XS
</label>
This way, you don't need to use the for and id attribute.
Also, among the radio buttons in the same button group, we don't need multiple required -- one is enough.
There was a problem hiding this comment.
wrapped radio button input inside label tag and removed redundant required, id and for attributes since label wrap inputs
<label>
<input type="radio" name="size" value="XS" required /> XS
</label>
|
@mo-omer
|
|
changed syntax on radio button to match the rest |
|
Changes look good. Well done. |

Self checklist
Changelist
included semantic wrappers for better grouping form controls and simpler code.