Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem appears to be an issue with your <a href="http://blacktiephotographers.com/wp-content/themes/photolux_v120/style.css" rel="nofollow noreferrer">style.css</a> file. In that file, you have:</p> <pre><code>/*::selection { background: #666; /* Safari */ color: #FFF; } ::-moz-selection { background: #666; /* Firefox */ color: #FFF; }*/ </code></pre> <p>What's happening is you have a comment <code>/* Safari */</code> 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.</p> <p>Removing the <code>/* Safari */</code> comment won't fix that problem, as the <code>/* Firefox */</code> below it causes the same issue.</p> <p><strong>EDIT:</strong> While that did fix a minor issue with the CSS, it wasn't the whole solution. In light of <a href="https://stackoverflow.com/users/551986/thakis">thakis</a>' answer below, fixing the following style does prevent the crashing when inspecting elements:</p> <pre><code>#navigation-menu-container{ border-image: url(images/shadow-border.png) 10 stretch; } </code></pre> <p>Compare <a href="http://jsfiddle.net/saluce/twkVp/" rel="nofollow noreferrer">this fiddle</a>, which is a copy/paste of the site code in question (all <code>head</code> tags and relevant html markup), with <a href="http://jsfiddle.net/saluce/twkVp/6/" rel="nofollow noreferrer">the corrected fiddle</a>, in which the <code>style.css</code> markup has been imported into the fiddle and the <code>#navigation-menu-container</code> rule has been changed to the above code, and you'll see that the fiddle page doesn't crash.</p>
    singulars
    1. This table or related slice is empty.
    1. PO'Aw, Snap!' Error when inspecting element in Chrome
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USsaluce
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO'Aw, Snap!' Error when inspecting element in Chrome
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI will try this, but would like to note that I get the error regardless of whether or not the dev. window is open. You may want to check on that again.
      singulars
      1. PO
      1. This table or related slice is empty.
    2. COUpdate: I removed all <script> tags from the main page, also removed a lot of the html - did this all through dev. tools "elements" tab - still get the same error.
      singulars
      1. PO
      1. This table or related slice is empty.
    3. COInteresting. I'm on version 21.0.1180.60, I wonder if that makes a difference. I know it was only erroring out on me with the dev window closed, but there might be something else besides that. If you are getting the error with it open or close, then test however way you can guarantee generating the error every time.
      singulars
      1. PO
      1. USsaluce
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload