Databases
StackOverflow2013
Postsdbo
POUnpredicted behavior of using non-unique IDs
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnpredicted behavior of using non-unique IDs
    primarykey
    data
    text
    <p>When people are saying that using identical id's for different DOM elements is wrong, I totally agree. I mean, there is no even something to discuss.</p> <p>But what is actually meant by the phrase "if you will have several eponymous ids on the page, that doesn't guaranteed to work"? </p> <p>What actually does not guaranteed to work? We can treat ID as a regular attribute, thus, we can find all divs that <code>document.querySelectorAll('[id="container"]')</code>. Accessing through getAttribute/setAttribute should work as well. If we are trying to fetch an element via <code>document.getElementById</code> - well, I haven't tested, but most probably selector engine will return first element it find traversing the tree. I can imagine this can not be guaranteed. What else?</p> <p>CSS will work pretty fine - <code>#container {background-color: "red"}</code> will paint with red all found containers (or am I wrong). Can somebody show me where in standard spec such behaviour is not guaranteed? </p> <p>So, what is actually not guaranteed? Once again, I do acknowledge the fact that using same IDs is wrong. Neither do I want discuss perfomance issues of applying id-heavy css rules. The question is about something which is quite similar to what C/C++ programmers call "unpredicted behavior".</p> <p><strong>UPD:</strong> If it sounds hard or even stupid for you, then well, just provide an examples of unpredictable ID related behavior in specific browser. At least, as for me, it is more useful answer than "well, anything is not guaranteed, how can not you get it!".</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USshabunc
    1. USshabunc
    plurals
    1. This table or related slice is empty.
    1. 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. POUnpredicted behavior of using non-unique IDs
      1. USwanovak
      1. VTFavorite
    2. VO
      singulars
      1. POUnpredicted behavior of using non-unique IDs
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POUnpredicted behavior of using non-unique IDs
      1. This table or related slice is empty.
      1. VTDownMod
    1. COSome browsers will handle differently & in some selector scenarios you'll get a group and other cases you'll get the first or last one. ie unpredictable, ie not garanteed to work.
      singulars
      1. POUnpredicted behavior of using non-unique IDs
      1. USGats
    2. CO@Gats, with all due respect, some browsers will do it wrong in some cases is not the clearest answer. I'm not drunk at all, may is it is just my bad english.
      singulars
      1. POUnpredicted behavior of using non-unique IDs
      1. USshabunc
    3. COAre you interested in how **specific** versions of **existing** browsers handle duplicate IDs? Or are you asking "what can generally go wrong if I do it"? The answer to the later question is clearly: "**Everything**".
      singulars
      1. POUnpredicted behavior of using non-unique IDs
      1. USJoachim Sauer
 

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