Is your goal to be able to disable the feature to prevent a late-known security issue?
Or is your goal to universally disable seamless for a port entirely? On Tue, May 1, 2012 at 2:06 PM, Maciej Stachowiak <m...@apple.com> wrote: > > On May 1, 2012, at 12:20 PM, Eric Seidel <e...@webkit.org> wrote: > >> Work is complete, fully working. Passing all the tests I could come up with: >> https://github.com/eseidel/webkit/compare/master...seamless >> >> I'm uploading and landing patches once reviewed again in bugzilla. >> >> I do not plan to add an ENABLE, as this work is complete and will all >> be landed by end of week, assuming timely reviews. > > I'd like to request an ENABLE for risk mitigation purposes (so anyone > shipping in the near future could turn it off without having to revert a > large patch set.) > > Regards, > Maciej > _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

