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

Native CSS nesting and View Transitions API (read description)

animation, sass/scss, solid-js
Brian Michael Poblete•490
@Brian-Pob
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


For this challenge, I decided to implement some cutting-edge CSS features. These are native CSS nesting and the View Transitions API. Note: as of the posting of this solution only Chromium supports the View Transitions API and not many browsers yet support native nesting. This is why the generated screenshot shows a broken UI.

I find native nesting really cool as it's an implementation of one of the coolest features of sass/scss. It makes it easier to keep your styles organized without having to duplicate a lot of code.

The View Transitions API makes animations easier to implement. I recommend reading this article by Jake Archibald at Google as well as the official MDN web docs page if you want to learn more about it. Btw, I helped edit the MDN page and my pull request got merged!

There are a couple of things that don't work as they should. I'm getting some very weird bugs with styles being applied to elements that don't have the associated class. Also, I did error handling differently from the way Frontend Mentor specifies.

And shoutout to Adam Argyle's Open Props for giving me some premade, easy-to-use animations via CSS variables.

Anyway, I found this challenge really fun. I learned a lot about native nesting and the view transitions api. If I were to keep working on this, I would probably almost completely rewrite it since using a lot of cutting-edge features at the same time isn't the best for compatibility. Also, my JavaScript could definitely be cleaned up.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Brian Michael Poblete'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.