6 ms·

Shadow DOM is a very, very bad idea. http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/ http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/ It

Shadow DOM is a very, very bad idea. http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/ http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/ It kills cross-browser compatibility, kills standards (since they're unreachable, undocumented elements that can handle input, interaction and affect other elements.

badman_ting 13y ago
It's starting to dawn on me what this will really be used for, and I can't say I'm stoked about it. But the article you've linked to seems pretty upbeat about the whole thing.
- grayrest 13y ago
  Author of the article is the spec author.
- donrhummy 13y ago
  I linked to an article that explains what it is and left it to you (the reader) to decide if it's good or bad. I believe it is a very bad thing.
ivan_gammel 13y ago
Even if it will become a standard, it may be complete evil. This concept is quite complicated for regular developer, so some day we'll see petabytes of cryptic, totally undebuggable markup. It should not be done in that way.