On Mon, Feb 13, 2012 at 1:02 PM, Maciej Stachowiak <[email protected]> wrote: > > I think you raise a good point. Another point worth mentioning is that > sometimes a feature can be complete and useful in one port, but half-baked > in another (for example, fullscreen API was shipped in Safari and at the > same time present but non-functional in Chrome). > > I think in the past, port owners have made clear that they want to own the > final decisions on what features are enabled in their ports. > > But we as a community could do better, by having a shared recommendation > of what features we think should be enabled in shipping releases. In some > cases, this may not match the settings on trunk, as some features may be > desirable to enable for experimental builds, but not in shipping product. > For features that we recommended disabling, ideally we'd identify a reason. > And in some cases, those might be port-specific issues. >
Right. Even just having a list of new features with flag(s) to enable/disable and the status (e.g. list of outstanding bugs) on wiki page will be helpful. For example, vertical writing mode doesn't work on Windows, Chromium, etc... but port owners may not necessarily realize that the feature is enabled by default and each port needs to modify the code that draws text. - Ryosuke
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
