4 ms·
The id attribute can take on values that are already present or reserved in window. "fetch", "opener", etc.. The reason to have a separate system that correct
by akira2501 2y ago
The id attribute can take on values that are already present or reserved in window. "fetch", "opener", etc..
The reason to have a separate system that correctly calls getElementById() is to avoid this issue.
So, it's actually a _less_ brittle mechanism that doesn't rely on legacy mechanisms and lacks the surprises that come with that.
- nattaylor 2y agoSorry, I didn't mean to suggest your solution was brittle -- I actually quite like it and want to adopt it! But I do think the legacy browser behavior with the ID attribute as window properties is very brittle for the reasons you suggest
- akira2501 2y agoMy fault, I tend to "rapid fire" sometimes. Yours was next to another reply on the identical subject and that caused me to mistake the meaning of the comma in your sentence. Reading it more slowly, I see it now, and, thank you!