Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h3>Update</h3> <p>This solution will not work for Chrome. It stops the loading indicator only when all requests made before window load have completed. The only solution appears to be to get it to make the request after window load, but as far as I know, this is only possible with setTimeout, which isn't great.</p> <hr> <h3>Update</h3> <p>To get around the pointer issue in Chrome, you could set the cursor style as shown in <a href="http://jsfiddle.net/7fDYE/19/" rel="nofollow">this fiddle</a>. It's a bit hacky and it doesn't address the issue of the loading indicator at the top of the tab.</p> <hr> <p>The loading indicator will be present in browsers until the page has loaded (window's load event). In <code>$(function(){someCode();});</code>, <code>someCode</code> is executed when the DOM load event is triggered (when all content has been parsed and inserted into the DOM, before page load). The execution of JavaScript at this point blocks the window's load event from firing, and so prevents the loading indicator from stopping. Note that image loading also blocks the window's load event.</p> <p>Instead, you could try <code>$(window).load(function(){someCode();});</code>. In this example, <code>someCode</code> is executed when the window's load event is triggered. This is at the point where the browser's loading indicator stops.</p> <p>So, instead of:</p> <pre><code>$(function(){ /*AJAX CODE HERE */ }); </code></pre> <p>Try:</p> <pre><code>$(window).load(function(){ /*AJAX CODE HERE */ }); </code></pre> <p>Note that this may cause your JavaScript to begin execution later, which may not be desirable.</p>
    singulars
    1. This table or related slice is empty.
    1. POChrome AJAX on page-load causes "busy cursor" to remain
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSpycho
    1. USSpycho
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf I understand you correctly, that does not work either, see how when using chrome the favicon and busy-cursor remain loading until the AJAX is finished. http://jsfiddle.net/mazlix/7fDYE/12/
      singulars
      1. PO
      1. USmazlix
    2. COSorry, it looks like Chrome doesn't stop the loading indicator until all JavaScript that began execution before the window load event finished bubbling has finished. So, if your script starts when window load occurs, it will block the loading indicator because window load hasn't finished when the script starts. Other browsers behave sensibly. It looks like the only way around this is with setTimeout (like [this](http://jsfiddle.net/ugTLz/3/)). It's not a great solution though... It will be hard to predict when the window load event will have finished and will mean content is loaded later.
      singulars
      1. PO
      1. USSpycho
    3. COis this a knwon chrome issue? or do they not consider it a bug? is there some other trick you can think of like body.hover() [except i assume that won't work for mobile devices]
      singulars
      1. PO
      1. USmazlix
 

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