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 8348309
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T07:39:12+00:00 2026-06-09T07:39:12+00:00

Whenever I inspect any element that’s part of my navigation menu, OR inspect element

  • 0

Whenever I inspect any element that’s part of my navigation menu, OR inspect element and then browse to a navigation menu I get the ‘Aw, Snap’ error in Google Chrome. I figured there must be something wrong with the source but after reviewing the source in an editor it seems as though everything is correct in format.

What might be causing this error?

You can Click Here to view the site 🙂

Update:

Something in this code here is causing the error:

<li>
    <a id="nav-corporate" class="accordionButton <?php if (is_page(1635) || is_page(1909)) { echo "curr-page-nav";}?>">Corporate</a>
<div class="sub-list-container">

    <ul>
        <li>
            <a href="<?php echo get_page_link(1635); ?>" id="nav-meeting" class="subitem"><span class="nav-hidden">Meetings</span></a>
        </li>
        <li>
            <a href="<?php echo get_page_link(1909); ?>" id="nav-event" class="subitem"><span class="nav-hidden">Events</span></a>
        </li>
    </ul>
    </div>
    </li>

I have tried on three computers by the way.

  • 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-09T07:39:13+00:00Added an answer on June 9, 2026 at 7:39 am

    The problem appears to be an issue with your style.css file. In that file, you have:

    /*::selection {
        background: #666; /* Safari */
        color: #FFF;
    }
    
    ::-moz-selection {
        background: #666; /* Firefox */
        color: #FFF;
    }*/
    

    What’s happening is you have a comment /* Safari */ within a broader comment around the entire snippet above, which is closing the broader comment prematurely and causing a parse error for the CSS. Google Chrome is choking on the malformed CSS file, which is causing the “Aw, snap!” error to occur when inspecting elements.

    Removing the /* Safari */ comment won’t fix that problem, as the /* Firefox */ below it causes the same issue.

    EDIT: While that did fix a minor issue with the CSS, it wasn’t the whole solution. In light of thakis‘ answer below, fixing the following style does prevent the crashing when inspecting elements:

    #navigation-menu-container{
      border-image:  url(images/shadow-border.png) 10 stretch;
    }
    

    Compare this fiddle, which is a copy/paste of the site code in question (all head tags and relevant html markup), with the corrected fiddle, in which the style.css markup has been imported into the fiddle and the #navigation-menu-container rule has been changed to the above code, and you’ll see that the fiddle page doesn’t crash.

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

Sidebar

Related Questions

Whenever I try installing anything using gem, I get this error - murtaza@murtaza-dev:~$ sudo
Whenever I do typedef std::vector< SomeType >::iterator I get the error: error: wrong number
Whenever I open some help within eclipse I get a page saying: Server Error.
Whenever I hit the sign in button I get the following error: NoMethodError in
Whenever I close XCode, the User Info entries that I set for attributes in
Whenever the activity that initiates the scan happens, the android application force closes. It
Whenever I try to Install my application on android emulator it gives error: no
Whenever I select an element in Internet Explorer, dotted lines appear around it, almost
Whenever I call folderbrowserdialog.showDialog() my application crashes. I'm using the code that worked before
Whenever I open IDEA it spends some time in indexing and then shows lots

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.