Skip to content

Comment on Ask HN: What are the technical reasons HTML inputs are impervious to CSS?

Comments

It's related to something called the Shadow DOM (http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/) (http://code.tutsplus.com/tutorials/intro-to-shadow-dom--net-...) and our friends the render-engine makers just had a big internal 'argument' about the wisdom of exposing it [Encapsulation !] and how. Where it is accessible -- Chrome -- things are pretty sketchy. Personally, I'd think long and hard before enabling it and all but Google [and Opera] seem to agree, but last I heard, 'we' are not going to have much say in the matter since Google announced they will go ahead with it unilaterally.

Thanks for the info. Do you know of a thread that contains this Google-lead debate? Or, are we talking about poking around the Chromium Github commits and reading between the lines?

It sounds like, with the shadow DOM, a lot of the discussion is about performance. I'd be curious how an element like a checkbox could have that much impact on performance even on mobile.

some of the 'debate' even spilled over here on HN : https://news.ycombinator.com/item?id=7243122

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.