El jue, 02-02-2012 a las 16:52 +0100, Xan escribió: > > > > - Rename current set_zoom_level and get_zoom_level as > > set_page_zoom_level and get_page_zoom_level > > - Add set_text_zoom_level and get_text_zoom_level > > - We save both values, but when one is set, the other one is reset > > (like it happens with apps calling > > webkit_web_view_set_full_content_zoom() all the time before setting the > > soom level) > > - That way we have both methods in the aPI and we avoid the setting. > > - If we eventually find a use case where it makes sense to set both at > > the same time we can just change the behaviour without having to change > > the API (just the impl and the documentation) > > > > Does it sound good? > > 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. > 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
