On Mar 9, 2013, at 5:02 PM, Maciej Stachowiak <m...@apple.com> wrote:
> > On Mar 8, 2013, at 3:09 PM, Adam Barth <aba...@webkit.org> wrote: > >> I've posted a patch to limit the -apple- and -khtml- CSS vendor >> prefixes to ENABLE(DASHBOARD_SUPPORT): >> >> https://bugs.webkit.org/show_bug.cgi?id=111890 >> >> My understanding is that I also need to add a runtime flag in order to >> fully hide these prefixes from the web because Safari and Dashboard >> share the same WebCore binary on Mac OS X. >> >> I found the following entry in Settings.in: >> >> usesDashboardBackwardCompatibilityMode initial=false, >> conditional=DASHBOARD_SUPPORT >> >> However, some of the paces we need to check this flag do not have easy >> access to the Page and therefore have trouble finding the Settings >> object. >> >> Would it be possible to use a global static flag to hide these >> prefixes from the web? I don't understand the details of how Safari >> and Dashboard share WebCore to know if a global static flag would work >> correctly. > > Safari and DashboardClient (the executable that actually renders widgets) > link the same copy of WebCore on disk, but are separate executables at > runtime. Dashboard backwards compatibility mode is triggered by the > per-WebView _setDashboardBehavior: call which then sets the > usesDashboardBackwardCompatibilityMode setting. It appears that any app using > this SPI either sets it on all WebViews or none I'm not sure that would be true for Dashcode. I could imagine that app setting Dashboard mode in its simulation views, but not in (say) a help viewing window. Simon
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
