Databases
StackOverflow2013
Postsdbo
POWhy is the # selector of lesser specificity than anything?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is the # selector of lesser specificity than anything?
    primarykey
    data
    text
    <p>Big bold caps-lock TL;DR:</p> <p><strong>I KNOW HOW SELECTOR SPECIFICITY IS DETERMINED, I THINK IT USES FLAWED ASSUMPTIONS AND I CAN BACK MY IRRITATIONS UP WITH VALID SET THEORY RELATIONS, PLEASE DO NOT RESPOND EXPLAINING W3 CALCULATION RULES FOR SPECIFICITY, PLEASE READ THE QUESTION</strong> &lt;- read that.</p> <p>This has bothered me for some time, when I write a style for some HTML that would be similar to below:</p> <pre><code>... &lt;div id="outer"&gt; &lt;span id="inner"&gt;&lt;/span&gt; &lt;span&gt;&lt;/span&gt; ... &lt;/div&gt; ... </code></pre> <p>Why would specificity rules make the selector "#outer span" more specific than "#inner"? ID's are unique, so when I say "#inner" I can ONLY be referring to one element, so why is it less specific? I understand the rules on determining specificity, I just wonder if this was intentional or accidental, also if anyone knows how I can ask this question to the people who write the css standards. </p> <p>I should note, I do understand that I COULD use #outer #inner to ensure maximum specificity, but that seems like it defeats the purpose of ID in the first place. This also is a problematic solution for when I write templates and I'm not sure that one ID will be inside of another. I'm not looking for a workaround, just a theory answer.</p> <p>My question is theory, entirely based on set logic. The though I have is that if you define a rule for 1 item of n possible items, isn't that as specific as you can go? Why would the creators of CSS selectors make a rule that could define m items of n possible items, where m is a subset of n as a more specific rule?</p> <p>My thought is that #id would be the equivalent of identifying 1 item by name, and #id elm would be identifying a group by its relation to an item by name. It's completely counter intuitive to call a named item less specific than an unnamed group with a named relation.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBoltClock
    1. USDavidJFelix
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is the # selector of lesser specificity than anything?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy is the # selector of lesser specificity than anything?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy is the # selector of lesser specificity than anything?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow do you come to this assumption?
      singulars
      1. POWhy is the # selector of lesser specificity than anything?
      1. USFelix Kling
    2. CO@Felix It goes totally against what I would have expected, but it's true. http://jsfiddle.net/DUKkT/
      singulars
      1. POWhy is the # selector of lesser specificity than anything?
      1. USPekka 웃
 

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