Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In most browsers, this can be achieved using proprietary variations on the CSS <code>user-select</code> property, <a href="http://www.w3.org/TR/2000/WD-css3-userint-20000216#user-select" rel="noreferrer">originally proposed and then abandoned in CSS3</a> and now proposed in <a href="https://drafts.csswg.org/css-ui-4/#content-selection" rel="noreferrer">CSS UI Level 4</a>:</p> <pre class="lang-css prettyprint-override"><code>*.unselectable { -moz-user-select: none; -khtml-user-select: none; -webkit-user-select: none; /* Introduced in IE 10. See http://ie.microsoft.com/testdrive/HTML5/msUserSelect/ */ -ms-user-select: none; user-select: none; } </code></pre> <p>For IE &lt; 10 and Opera &lt; 15, you will need to use the <code>unselectable</code> attribute of the element you wish to be unselectable. You can set this using an attribute in HTML:</p> <pre><code>&lt;div id="foo" unselectable="on" class="unselectable"&gt;...&lt;/div&gt; </code></pre> <p>Sadly this property isn't inherited, meaning you have to put an attribute in the start tag of every element inside the <code>&lt;div&gt;</code>. If this is a problem, you could instead use JavaScript to do this recursively for an element's descendants:</p> <pre><code>function makeUnselectable(node) { if (node.nodeType == 1) { node.setAttribute("unselectable", "on"); } var child = node.firstChild; while (child) { makeUnselectable(child); child = child.nextSibling; } } makeUnselectable(document.getElementById("foo")); </code></pre> <hr> <p><strong>Update 30 April 2014</strong>: This tree traversal needs to be re-run whenever a new element is added to the tree, but it seems from a comment by @Han that it is possible to avoid this by adding a <code>mousedown</code> event handler that sets <code>unselectable</code> on the target of the event. See <a href="http://jsbin.com/yagekiji/1" rel="noreferrer">http://jsbin.com/yagekiji/1</a> for details.</p> <hr> <p>This still doesn't cover all possibilities. While it is impossible to initiate selections in unselectable elements, in some browsers (IE and Firefox, for example) it's still impossible to prevent selections that start before and end after the unselectable element without making the whole document unselectable.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to disable text selection highlighting?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Down
    1. USTim Down
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyou should remove the * selector from your example, its really in-efficient and there really isnt any need to use it in your example is there?
      singulars
      1. PO
      1. USBlowsie
    2. CO@Blowsie: I don't think so: the CSS 2 spec states that `*.foo` and `.foo` are precisely equivalent (in the second case, the universal selector (`*`) is implied), so barring browser quirks, I can't see that including the `*` will harm performance. It's a long-standing habit of mine to include the `*`, which I originally started doing for readability: it explicitly states at a glance that the author intends to match all elements.
      singulars
      1. PO
      1. USTim Down
    3. COoooh after some further reading, it seems * is only un-effiecient when using it as the key (the righmost selector) ie .unselectable * . Further info here http://code.google.com/speed/page-speed/docs/rendering.html#UseEfficientCSSSelectors
      singulars
      1. PO
      1. USBlowsie
 

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