Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8339641
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T04:56:09+00:00 2026-06-09T04:56:09+00:00

This may be a silly question (aren’t they all?), but I’ve been stumped on

  • 0

This may be a silly question (aren’t they all?), but I’ve been stumped on something for a while now…
I’m trying to build a lightbox-type pop-up for displaying details about a list item in a definition list. I’ve got the fadeIn and fadeOut working correctly, but I’m getting bugs if I try to trigger the same even on a different list item while the pop-up is still active.

Here’s the code I’m working with…

    <html>, etc...
    <div>
       <dl>
        <dt>Trigger Element</dt>
        <dd>
            <div>
            (lightbox content)
            </div>
        </dd>
       <dl>
        <dt>Trigger Element</dt>
        <dd>
            <div>
            (lightbox content)
            </div>
        </dd>
       Etc....
     </dl>

 (function() {
    // Highlight the target dt items
    $('div.cigar-pop').parent().prev().addClass('cigar-highlight');

    // Initialize the lightbox functionality
    $('dd').children('div').addClass('hidden');
    $('dt').on('click', function() {
        //I'm still not entirely sure why this part worked...
        var $this = this;
        $(this).next()
            .children('div')
                .addClass('active')
                    .fadeIn(800, function($this) {
                        $('body').one('click', function(){ 
                            $('.active').fadeOut('fast')
                                .removeClass('active');
            });
        });
    });

    })();

I’m betting it’s something simple, but I can’t figure out what. Sorry if this is a little rudimentary for this forum’s unparalleled genius 😛

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T04:56:12+00:00Added an answer on June 9, 2026 at 4:56 am

    You could add a check to see if there’s an .active element already, and just return.

    $('dt').on('click', function() {
        if($('.active').length) return; // do not return false;
        // Your code
    

    This will prevent the rest of your code in this function block from executing. In other words, when there is an .active element, the behaviour of clicking on another dt would be to hide the current .active element, rather than show a new one.

    The reason we don’t return false; is that this would stop the event from propagating, which is what we need it to do to reach the body, so the current .active element gets removed/hidden.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This may be a really silly question but it's something I've been struggling with.
This may be a silly question, but I'm not all too experienced with iPhone
This may be a silly question, but right now I have a rather large
Now this may seem like a silly question, but I need to know how
This may be a silly question, but I haven't been able to find the
This may seem a silly question, but having been pondering it for a few
This may be a silly question (with MSDN and all), but maybe some of
Now, this may be a silly question but sometimes the terms Framework and API
This may seem like a silly question, but it is something that drives me
This may be a silly question, but it's been bugging me. I've been writing

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.