Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think the idea of "why" is more a "generational" or "authority" view point. If <code>#Parent</code> (of any generation back) says all my children who meet qualification "x" (in your case, <code>span</code>) are going to be given an inheritance of "y" (whatever css property), it doesn't matter what the single individual <code>#Child</code> wants, it needs the authority of the <code>#Parent</code> to get it if the parent has stated otherwise.</p> <p><strong>Added on edit:</strong> The inline <code>style</code> would then be the rebellious child, and the <code>!important</code> the crack down parent. <em>Edit:</em> I kept this for humor, but I don't think it reflects the idea as well as my later statement below.</p> <p><strong>Added on edit to question in comment:</strong> Given:</p> <pre><code>#outer span ... #inner (which is a span element) </code></pre> <p>Then to help insure #inner selection I recommend:</p> <pre><code>body span#inner (*edit:* just span#inner works *edit:* if defined later) </code></pre> <p>or give body an id and</p> <pre><code>#bodyId #inner </code></pre> <p>Of course, these can still be overridden. The more "generations" involved, the more it becomes difficult to change the behavior because of the generational consensus (if great grandpa and grandpa and parent are all in agreement, it's likely the child is not going to get away with doing his own thing).</p> <p><strong>I had to majorly rewrite this section on later edit</strong> Given this HTML:</p> <pre><code>&lt;div id="grandparent"&gt; &lt;div id="parent"&gt; &lt;div id="child"&gt;&lt;/div&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p>I had previously stated that "<code>#parent div</code> has greater authority than <code>#grandparent div</code>. Both have generational authority, in fact, an 'equal' generational authority, but the first is 'nearer' generation" wins. <em>The error</em> in that is that "nearer" generationally is not what matters, but rather last to be granted authority. Given equal authority powers, the own designated last is the one that wins.</p> <p>I believe I can still stand by this statement: With that thought in mind, a selector like #child[id] (which outweighs both previous selectors) treats its attributes as permissions for greater authority to rule that which itself controls. Having the # already gave it authority, but not enough to override a # of a earlier generation if that earlier generation also carries another selector granting more authority.</p> <p>So <code>#grandparent div</code> outweighs <code>#child</code> but not <code>div#child</code> <em>if it is last to receive authority [added this]</em>, and not <code>#child[id]</code> because the <code>[id]</code> adds greater authority for the <code>#child</code> to rule itself. If equal selectivity then last one to be granted authority wins.</p> <p>Again, the <code>style</code> attribute setting a style property itself really acts more like a supreme granting of authority to rule oneself, assuming something more "<code>!important</code>" doesn't take it away.</p> <p>As a summary statement to answer "why" it is this way (and not in line with "set" theory), I believe it is not about <em>accuracy</em> or really even <em>specificity</em> (though that is the term used) as indeed then one would expect <code>#ChildsName</code> to be the final unique say in the matter because nothing more specific need be said. Rather, however, while the documentation may not state it as such, "selectivity" is really structured on a granting of <em>authority</em>. Who has the most "rights" to rule the element, and given a "tie", who was the last one to be granted those rights.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy is the # selector of lesser specificity than anything?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USScottS
    1. USScottS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy is the # selector of lesser specificity than anything?
      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. 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. COI do like this explanation a bit, but it seems as though there are plenty of ways to say "all children of x parent act in y way" while it's difficult to just say "this specific item, act this way" and be certain that it will, even though i could identify it by name. I won't write a rule for #child if I don't want it to act that way.
      singulars
      1. PO
      1. USDavidJFelix
    2. COI'm out of post votes for the day, but I think you kind of nailed it. Also, your addendum is amusing yet true.
      singulars
      1. PO
      1. USBoltClock
    3. COI see it more like using the #Parent is giving it the generational authority, whereas the #Child alone is acting without parental authority (self authority) and is fine to do so as long as the parent has not said otherwise. So in other words, you, the author are not the parent, the #Parent container is. If you, the "outsider" want to command the #Child what to do, you have to do it through the parental authority if the parent has laid down other rules that might contradict.
      singulars
      1. PO
      1. USScottS
 

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