On Wed, Aug 15, 2012 at 12:55 PM, Darin Adler <da...@apple.com> wrote: > On Aug 14, 2012, at 5:41 PM, Elliott Sprehn <espr...@chromium.org> wrote: > >> The point of the vendor prefix is to assert the instability of the feature. > > The WebKit project uses vendor prefixes to avoid compatibility conflict > between a feature and a later incompatible standardized feature that would > use the same name. This is not intended as a way to smuggle in low quality > features. > > WebKit features should have high quality implementations even during the > stage where they are vendor-prefixed. We don’t want to ship half-baked or low > quality features in releases of WebKit because they can cause long term > problems for people supporting content that has to work on multiple versions > of WebKit. > > -- Darin
Sorry, but I honestly don't see the point of this discussion anymore, in terms that all the implementations are getting proper layout tests (property usage, repaint, getComputedStyle, etc) and pending review. The compile flag (now accepted by all) is being addresed in https://bugs.webkit.org/show_bug.cgi?id=93863 and thus won't make the feature exposed to web by default. As Ryosuke mentioned, layout tests aren't enough for properly testing editing features, so please point me to where I can actually stress test it to get confidence about the code. Best, -- Bruno de Oliveira Abinader _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
