Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add task solution #4483

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

alena-bondar
Copy link

  • DEMO LINK

  • TEST REPORT LINK

  • [ x ] Icon implemented using background-image CSS property

  • [ x ] Inputs are written inside of 'form' tag with correctly passed attributes

  • [ x ] All Typical Mistakes from BEM lesson theory are checked.

  • [ x ] Code follows all the Code Style Rules ❗️

Copy link

@mateacademy-ai-mentor mateacademy-ai-mentor left a comment

Choose a reason for hiding this comment

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

Great job on your Pull Request! 🌟 The issues mentioned are minor and don't significantly impact the functionality or security of your code. For future projects, consider the feedback on HTML formatting and CSS best practices to enhance the readability and maintainability of your code. Keep up the good work! 💻🚀

✨ Please rate this review in the Platform's notification center. I will be grateful for your feedback! ✨

Comment on lines +20 to +22
<form
class="search-form search-form__big"
data-qa="big"

Choose a reason for hiding this comment

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

HTML Formatting: The attributes of the <form> element should each start on a new line with 2-space indentation, and the closing bracket should be aligned with the opening tag. This will improve readability and maintain consistency with proper HTML formatting.

class="search-form search-form__big"
data-qa="big"
>
<label class="search-form__label search-form__label_big">

Choose a reason for hiding this comment

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

HTML Formatting: The <label> element should be indented with 2 spaces inside its parent <form> element to maintain proper nesting and readability.

Comment on lines +25 to +29
<input
type="text"
data-qa="keypress"
class="search-form__input search-form__input_big"
placeholder="Try “Los Angeles“"

Choose a reason for hiding this comment

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

HTML Formatting: The attributes of the <input> element should each start on a new line with 2-space indentation, and the closing bracket should be aligned with the opening tag. This will improve readability and maintain consistency with proper HTML formatting.

Comment on lines +34 to +36
<form
class="search-form search-form__small"
data-qa="small"

Choose a reason for hiding this comment

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

HTML Formatting: The attributes of the <form> element should each start on a new line with 2-space indentation, and the closing bracket should be aligned with the opening tag. This will improve readability and maintain consistency with proper HTML formatting.

class="search-form search-form__small"
data-qa="small"
>
<label class="search-form__label search-form__label_small">

Choose a reason for hiding this comment

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

HTML Formatting: The <label> element should be indented with 2 spaces inside its parent <form> element to maintain proper nesting and readability.

Comment on lines 19 to 47
<body>
<input
type="text"
data-qa="keypress"
placeholder="Try “Los Angeles“"
/>
<form
class="search-form search-form__big"
data-qa="big"
>
<label class="search-form__label search-form__label_big">
<input
type="text"
data-qa="keypress"
class="search-form__input search-form__input_big"
placeholder="Try “Los Angeles“"
/>
</label>
</form>

<input
type="text"
data-qa="hover"
placeholder="Try “Los Angeles“"
/>
<form
class="search-form search-form__small"
data-qa="small"
>
<label class="search-form__label search-form__label_small">
<input
type="text"
data-qa="hover"
class="search-form__input search-form__input_small"
placeholder="Try “Los Angeles“"
/>
</label>
</form>
</body>

Choose a reason for hiding this comment

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

HTML Formatting: Add empty lines between multiline sibling blocks of HTML to add some 'air' and simplify reading, but don't add them between parent and child elements.

Comment on lines +15 to +17
* {
box-sizing: border-box;
}

Choose a reason for hiding this comment

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

Avoid using the * selector as it impacts performance. Set styles only for elements that require them.

margin: 8px;
padding: 0;
font-size: 16px;
font-family: Avenir, sans-serif;

Choose a reason for hiding this comment

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

Remember to specify fallback fonts. For instance, font-family: Avenir, Arial, sans-serif; ensures that if the primary font isn't available, the browser can use a similar fallback.

Comment on lines +23 to +24
font-family: Avenir, sans-serif;
font-weight: 300;

Choose a reason for hiding this comment

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

Be consistent with your margins to avoid potential margin collapse. It's better to add only top or bottom margins but not both, and in this case, you have set the margin on the body which could lead to unexpected results when combined with other margins.

.search-form {
display: flex;
justify-content: center;
margin: 20px auto 0;

Choose a reason for hiding this comment

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

Don't fix container sizes unless required. Here, the .search-form has a fixed margin, which might not be necessary. Let the content size dictate the container size to avoid overflow or accidental scroll bars.

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

Successfully merging this pull request may close these issues.

2 participants