El jue, 02-02-2012 a las 17:09 +0100, Xan escribió: > On Thu, Feb 2, 2012 at 4:57 PM, Carlos Garcia Campos <[email protected]> > wrote: > >> Unfortunately I think that still would count as an API break. Changing > >> how the API behaves is an API break, even if your application still > >> compiles. So it's not as safe as you make it sound, IMHO. Considering > >> that I'm not really sure that it's worth it to change the current API, > >> if I'm understanding things correctly. > > > > Of course, I actually meant if we eventually decide to support it > > *before* the first stable release of WebKit2. > > I see, makes more sense then. > > I think this is probably reasonable as long as there's still an API to > ask WebKit what kind of zoom is in effect. Otherwise you'd always need > to remember on the application side.
Since setting one resets the other, the one returning something different than 1 is the effective one. If both return 1, no scale factor is applied so the assumption is still valid. > Xan > -- Carlos Garcia Campos http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3
signature.asc
Description: This is a digitally signed message part
_______________________________________________ webkit-gtk mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-gtk
