Core CSS Conflict – .hidden Class?

This topic contains 5 replies, has 3 voices, and was last updated by  Patrik 5 years, 7 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: , ,

  • Author
    Posts
  • April 2, 2019 at 7:58 pm #477617

    Brent Barkley
    Expired Member
    Post count: 7

    Hello. We’ve attempted all the normal courses of action (plugin conflict, etc.) to isolate a problem we’re having with a custom theme and GeoDirectory.

    We’ve narrowed it down to the gd_core_frontend.css file, specifically the .hidden class. No other plugin or script on our site uses that class, but we get a white screen for every page on our site unless we remove that class from GeoDirectory’s core stylesheet. Interestingly, the markup doesn’t have a .hidden class anywhere despite it affecting every page on the site

    Any ideas of what this conflict could be?

    April 2, 2019 at 8:12 pm #477621

    Kor
    Moderator
    Post count: 16516

    Hi Brent Barkley,

    Thanks for your post. Could you possibly share your Website URL here in question so that we could check this out for you?

    Thanks!

    April 2, 2019 at 8:15 pm #477623

    Brent Barkley
    Expired Member
    Post count: 7
    This reply has been marked as private.
    April 3, 2019 at 6:27 am #477731

    Patrik
    Moderator
    Post count: 1971

    Hi Brent,

    Our plugin has CSS for the .hidden class which hides the element. I want to troubleshoot why the hidden class is added to your <html> tag as GD doesn’t add such class to <html> tag by default.

    Regards,
    Patrik

    April 3, 2019 at 6:36 am #477734

    Brent Barkley
    Expired Member
    Post count: 7

    It’s coming from Modernizr.

    “Looking through the Modernizr download page, it looks like the “hidden” class is added when Modernizr is checking for and detects support for the [hidden] attribute.”

    I can of course customize Modernizr to remove that attribute. But it seems like maybe it’s better in the future to use a less likely conflict name like .gd-hidden or similar in your plugin? .hidden class is likely to be a pretty popular name to hide things and could lead to issues like this. Thanks for helping me identify though–your comment about the HTML tag (I had missed that) led me in the right direction.

    April 3, 2019 at 10:41 am #477809

    Patrik
    Moderator
    Post count: 1971

    Hi,

    Good to know that you found a solution. We will take a note of this and will update the plugin based on that.

    Regards,
    Patrik

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount