Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

Using JavaScript and CSS to toggle notification elements.

Amhed Hussien•390
@Eng-Ahmed-Hussien
A solution to the Notifications page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm most proud of how the Notifications Page effectively uses JavaScript and CSS to toggle notification states. The seamless transition between unread and read notifications—coupled with the "Mark all as read" functionality that updates the unread count—is a highlight of this project. The clear visual cues (such as the red dot styled in CSS) provide immediate feedback and enhance the overall user experience.

Next time, I would:

  • Refine the interface with subtle animations during state transitions.
  • Improve code modularity in JavaScript to make the toggling functionality even more scalable.
  • Enhance accessibility by incorporating additional ARIA attributes and better focus management for keyboard users.
What challenges did you encounter, and how did you overcome them?
  • State Management:
    Managing the toggle between unread and read states was challenging. I resolved this by using JavaScript to add or remove the unread class from notification elements and update the top bar counter dynamically with the updateTopBar() function.

  • Visual Consistency:
    Ensuring consistent styling across different devices required careful tuning of CSS properties (e.g., using .notification.unread and .red-dot). Iterative testing and adjustments helped me achieve a balanced design.

  • Event Handling:
    It was crucial to ensure that only the intended elements responded to click events. By checking if (e.target.tagName !== "A") in the event listener, I prevented unwanted interactions and maintained a smooth user experience.

What specific areas of your project would you like help with?

I appreciate any feedback or suggestions to help refine and improve this project further!

  1. Enhanced Animations and Transitions:

    • What are some best practices for adding smooth animations when notifications toggle their state?
    • Would leveraging CSS transitions or a JavaScript animation library improve the visual feedback?
  2. JavaScript Modularity and Optimization:

    • Are there design patterns or techniques you would recommend to further modularize the notification toggling logic?
    • Would using ES6 modules or a modern framework enhance maintainability?
  3. Accessibility Improvements:

    • Which additional ARIA attributes or semantic HTML enhancements would you suggest to improve accessibility for interactive notifications?
    • How can focus management be optimized to ensure a seamless experience for keyboard and screen reader users?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Amhed Hussien's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.