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

Browser Extensions Manager UI • ES6 Modules & CSS Custom Properties

fetch
Thiago Lorhan•150
@Thiagouh
A solution to the Browser extension manager UI 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 cleanly I modularized the JavaScript into ES modules—separating cards, filters, theme toggling, and animations into their own files. That separation made it much easier to reason about each piece and to find bugs quickly. I also tackled the smooth “slide-out” animations by listening for the animationend event rather than hard‑coding timeouts, which gave the UI a very polished feel.

Next time, maybe I’d set up ESLint, Prettier, and/or Husky before I ever wrote a line of code so I’d never slip in typos like toUppercase() or miss backticks in the README. I’d also integrate a lightweight bundler (e.g. Vite) early on to avoid the trial‑and‑error of fixing relative paths for assets on GitHub Pages.

What challenges did you encounter, and how did you overcome them?
  1. Relative asset paths on GitHub Pages I kept getting 404s for my icon paths because I was treating them as if they resolved from the JS file’s folder, not the HTML’s base URI. I diagnosed it in DevTools (inspecting the src on the <img>), learned how document.baseURI works, and finally switched to ./assets/images/... from the page root.

  2. Toggling icons vs. system media queries Using <picture> with prefers-color-scheme forced the browser to ignore my JS‑driven theme toggles. The fix was to remove the <source> tags altogether and manage the <img>’s src entirely in code, giving me full control.

  3. Off‑by‑one in filtering logic My first filter callback forgot to declare (item) =>, so item was undefined and no cards ever rendered. Once I caught that in the console, it was a quick fix—but a good reminder to write small, testable functions.

What specific areas of your project would you like help with?
  1. Unit testing strategy I’d love guidance on writing Jest tests for DOM‑heavy modules. For example, how to simulate clicks on the filter buttons and assert that only the correct cards remain.

  2. Optimal bundler setup Recommendations on a minimal Vite or Webpack config that handles ES modules, hot reloading, and static assets (images, fonts) without too much boilerplate.

  3. Accessibility improvements Feedback on additional ARIA attributes or keyboard‑navigation patterns for the card list and theme toggle beyond the aria-label I already added.

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 Thiago Lorhan'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.