Re^5: Approved PM markup: div but not span?

in reply to Re^4: Approved PM markup: div but not span?
in thread Approved PM markup: div but not span?

If id were allowed, that would allow id collisions, ... could be used for attribution confusion, navigation hazards and other tricky annoyances

Really? I mean, really, really!?

I know that lore has it that duplicate ids in html is verboten -- although HTML5 relaxed the specification to:

The value must be unique amongst all the IDs in the element's home subtree and must contain at least one character

with duplicates in a given subtree being ignored. -- but is the possibility of duplication -- accidental or deliberate -- so heinous that we must prevent it at all costs?

Isn't the worst that could happen is that the duplicates might both get styled the same way?

I could (vaguely) understand the restriction if this place was a JQuery-driven game-show site, like so many are these days; but as-is, and seems likely as-always-will-be, isn't the banning of ids just another piece of over-zealous control-freakery?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!

In Section Perl Monks Discussion