Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Mobile-first FAQ accordion

Ify Nonyelu•260
@Yetco
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I found it difficult to add the transition and ease in when you click on a question. I couldn't figure it out.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Weston Vincze•30
    @WestonVincze
    Posted over 1 year ago

    No worries! Happy to help. I took a look at the code and found the issue.

    This is the culprit.

    const questionHideContent = question.querySelector(".hide");

    The issue here is that querySelector only checks child nodes and .hide is actually a sibling.

    To solve this, all we have to do is change the above line to:

    const questionHideContent = question.parentNode.querySelector(".hide");

    As a side note, your solution no longer requires the active class, since it was previously used to determine whether or not .hide should be hidden or not.

    Marked as helpful
  • Weston Vincze•30
    @WestonVincze
    Posted over 1 year ago

    Adding transitions for an accordion is a bit tricky. In order for the text content to slide in and out you'll want to animate the max-height of the element.

    First, add this to your .hide class:

    .hide {
      max-height: 0;
      overflow: hidden;
      transition: max-height 0.3s ease-in-out;
    }
    

    Next, remove display: none from your hide class as well, otherwise the content will be instantly hidden without any animation.

    The last part is where it gets a little tricky... we need to set a max-height for the content while the parent is active. An easy way to do this is to simply set the max-height to be higher than any of the content (something like 500px):

    .active .hide {
      max-height: 500px;
    }
    

    However, you may notice that an odd delay occurs. That's because the animation goes from 0px to 500px and vice versa regardless of the actual height of the content. Basically, if your content is 300px high, the animation will act as if it was 500px.

    The better solution is to use JS to dynamically assign the max-height based on the content of each .hide by using its scrollHeight.

    // check if the parent is active
    const isActive = answer.parentNode.classList.contains("active");
    
    // if it is active, set the max height to the height of its scrollable content
    answer.style.maxHeight = isActive ? `${answer.scrollHeight}px` : 0;
    

    Note: answer represents a single instance of a .hide element. You'll have to iterate through answers just like you did for questions.

    Hopefully that helps! Let me know if you have any questions about my explanation.

    Marked as helpful

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

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.

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