Skip to content

solution#1801

Open
Kit3AWP wants to merge 2 commits intomate-academy:masterfrom
Kit3AWP:develop
Open

solution#1801
Kit3AWP wants to merge 2 commits intomate-academy:masterfrom
Kit3AWP:develop

Conversation

@Kit3AWP
Copy link
Copy Markdown

@Kit3AWP Kit3AWP commented Apr 12, 2026

- [DEMO LINK](https://Kit3AWP.github.io/js_notification_DOM/)

Copy link
Copy Markdown

@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.

Review Summary

I am requesting changes because your notifications currently miss an inline position: absolute style, which causes three Cypress tests (success, error, warning message specs) to fail. In src/scripts/main.js, inside your pushNotification (or equivalent) function where you set notification.style.top = ... and notification.style.right = ..., you only apply top and right but not position, so the element’s style attribute ends up as top: 10px; right: 10px; instead of the required position: absolute; top: 10px; right: 10px;. This violates the task’s expectations as encoded in the tests, so it is a functional blocker rather than a cosmetic difference. To fix this, add notification.style.position = 'absolute'; (or the equivalent for your variable name) alongside your existing top and right assignments so that all three notifications (success at 10px, error at 150px, warning at 290px) have the exact style string the tests assert. Aside from this missing inline position property, your implementation correctly creates the notification DOM structure, applies the required classes, and hides each notification after 2 seconds without removing it from the DOM, which is all good. Once you add the inline position: absolute, the failing end‑to‑end tests should pass and your solution will fully meet the task requirements.


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

Important

Fix the issues, commit the changes, and then re-request my review using the Re-request review button2 in the Reviewers tab.

Tip

If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag3.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.

Caution

Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.

Footnotes

  1. Rate AI review example

  2. Re-request AI review example

  3. Add AI review comments example

Copy link
Copy Markdown

@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.

Review Summary

I am requesting changes because there is a single critical issue that will cause the tests to fail: the inline style applied to each notification is missing position: absolute, which the tests expect to see in the exact style string. In src/scripts/main.js, in the pushNotification function where you currently set the style (likely via notification.setAttribute('style', ...)), you only set top and right but not position. The task requires the notification to have inline styles like position: absolute; top: 10px; right: 10px; (or equivalent values), and the automated tests compare that style string directly, so omitting position: absolute breaks the required behavior. To fix this, update that line so position: absolute is included in the same style string, or set it just before with something like notification.style.position = 'absolute'; and ensure the final style attribute matches what the tests assert. Everything else in your implementation looks solid: you create the correct DOM structure, apply the right classes, and hide notifications after 2 seconds without removing them from the DOM. Once you add position: absolute to the inline style for all notifications in pushNotification, your solution should meet the requirements and pass the tests. Keep going—you’re very close and only need this small but important adjustment.


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

Important

Fix the issues, commit the changes, and then re-request my review using the Re-request review button2 in the Reviewers tab.

Tip

If you have any comments about this review, please leave a message in the Add a comment section below and mention me with the @mateacademy-ai-mentor tag3.
I will read your message during my next review of your pull request. Please do not reply directly to my comments, as that feature is not supported yet.

Caution

Do not close the pull request until the review is complete. Closing it early can lead to unexpected behavior and disrupt the review process.

Footnotes

  1. Rate AI review example

  2. Re-request AI review example

  3. Add AI review comments example

const topValue = typeof posTop === 'number' ? `${posTop}px` : posTop;
const rightValue = typeof posRight === 'number' ? `${posRight}px` : posRight;

notification.setAttribute('style', `top: ${topValue}; right: ${rightValue};`);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The inline style for the notification is missing position: absolute. Update this line so the style includes position: absolute; top: ...; right: ...; (or set notification.style.position = 'absolute' before appending). The tests expect an exact style string with position: absolute present for all notifications.

Copy link
Copy Markdown

@brespect brespect left a comment

Choose a reason for hiding this comment

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

Well done!

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.

3 participants