I think it would be better to remove this code in controlled pieces along with all the underlying implementation (which is mostly not behind the flag) rather than removing it wholesale. It is good to understand what we are removing and that gets difficult if the API level (the only thing consistently behind SHADOW_DOM) is not present. I was also considering leaving a basic implementation along the lines of http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0387.html in place (mostly to keep <details> element working).
antti On Thu, May 16, 2013 at 8:09 PM, Ryosuke Niwa <[email protected]> wrote: > Hi, > > It appears that not a single port enables SHADOW_DOM build flag at this > point, and WebKit doesn't even compile with that option enabled. (There are > a few dozens of build failures). > > Is anyone intending to maintain the feature on trunk? If not, we should > simply get rid of code behind this build flag for now; keeping unmaintained > code that doesn't even compile isn't healthy for the project of our size. > > - R. Niwa > > > _______________________________________________ > webkit-dev mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
