[Edbrowse-dev] id not unique

[Edbrowse-dev] id not unique

[Karl Dahlke]

I'm pretty sure I read, in multiple places, that the id=foo attribute was suppose to be unique across the document.
<div id=foo>
In support of this notion, there is the function document.getElementById("foo") which returns that node.
It's not elementsById, like getElementsByTagName and the others, this one is singular,
the only one that is singular in the group, because there is one node per id.
However ... here we go ...
www.ibm.com has many overloads, which show up with db3.
There are 4 <h2 id=ibm-section-h2> headings.
edbrowse currently returns the last one via getElementById("ibm-section-h2"),
while document["ibm-section-h2"] points to the first one.
Inconsistent, yes, but I didn't thing this was suppose to happen at all so I didn't plan for it.
More fallout: when I was trying to process all the css descriptors, and building hash tables etc,
I optimized #foo to grab the one and only node returned by getElemenById(). That's wrong.
That code isn't being used right now, so querySelectorAll("#ibm-section-h2") returns all 4 nodes, which is correct.
If I move forward and process at least some of the css at document load time, I need to bear this in mind.
Not really saying theres a bug or problem here, just thinking out loud.

Karl Dahlke

Re: [Edbrowse-dev] id not unique

[Kevin Carhart]

edbrowse is on fire, seriously.  At this point in the story of the 
inventor who discovers antigravity or cold fusion, someone pays them a 
visit in an unmarked car.  What ensues is either not very pleasant, or 
they are offered a million dollars.  (Or both.)



On Fri, 23 Feb 2018, Karl Dahlke wrote:

> I'm pretty sure I read, in multiple places, that the id=foo attribute was suppose to be unique across the document.
> <div id=foo>
> In support of this notion, there is the function document.getElementById("foo") which returns that node.
> It's not elementsById, like getElementsByTagName and the others, this one is singular,
> the only one that is singular in the group, because there is one node per id.
> However ... here we go ...
> www.ibm.com has many overloads, which show up with db3.
> There are 4 <h2 id=ibm-section-h2> headings.
> edbrowse currently returns the last one via getElementById("ibm-section-h2"),
> while document["ibm-section-h2"] points to the first one.
> Inconsistent, yes, but I didn't thing this was suppose to happen at all so I didn't plan for it.
> More fallout: when I was trying to process all the css descriptors, and building hash tables etc,
> I optimized #foo to grab the one and only node returned by getElemenById(). That's wrong.
> That code isn't being used right now, so querySelectorAll("#ibm-section-h2") returns all 4 nodes, which is correct.
> If I move forward and process at least some of the css at document load time, I need to bear this in mind.
> Not really saying theres a bug or problem here, just thinking out loud.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>

---