GNOME Bugzilla – Bug 503967
epiphany-webkit: text resize does not work.
Last modified: 2008-12-15 15:43:34 UTC
this is the second problem i ran into with epiphany-webkit. the text resize feature does not work. ctrl++, ctrl+-, ctrl+mwheelup, ctrl+mwheeldown, and the view menu "larger text" and "smaller text" options do not do anything. this is debian bug 452762 (http://bugs.debian.org/452762). thanks again for all the hard work.
This is due to http://bugs.webkit.org/show_bug.cgi?id=14998, currently WebKit/GTK+ misses a zoom feature.
Marking NOTGNOME.
Reinouts, we'll still need to do some things on our side (as in most of the other webkit bugs), so it's good to keep them open I'd say. Reopening.
http://bugs.webkit.org/show_bug.cgi?id=14998 has been fixed but for now WebKit gtk is lacking an API to use zooming, adding this API is tracked by http://bugs.webkit.org/show_bug.cgi?id=14998 I'm probably going to make full-page zoom the default and text-only scaling (like in gecko) usable setting a property on the webview if other WebKit developers agree with me. What do you think? Do epiphany developers have any preference?
I would prefer having both kinds of zoom available in the API. Epiphany itself will probably only offer text-zoom in its UI.
For us it makes more sense to have text-only as default, if they must share the API. As chpe says it would make sense to offer both and let embedders pick what they want to do...
I was hoping to convince you to use full-page zoom as the default :) The API will offer both but you cannot you them at the same time. Safari will use text-only zoom but the mode can be changed modifying a key with their equivalent of gconftool.
Why can't text-zoom and full-zoom be used at the same time? They're clearly orthogonal features.
there are some other issues related to fonts, but i'm not sure if they should be associated with this bug or if a new bug should be opened. the issues are: 1. choosing language-specific fonts doesn't work. if you go to Edit -> Preferences -> Fonts & Styles -> Detailed Font Settings you can change the settings there, but they will have no effect. the same can also be said for Edit -> Preferences -> Language -> Encodings. you can change the default language encoding, but it has no effect. 2. choosing language-specific minimum font size doesn't work modifying Edit -> Preferences -> Fonts & Styles -> Minimum size doesn't have any effect. this may in fact be related to the text zoom capabality. 3. web pages can't specify their own fonts Edit -> Preferences -> Fonts & Style -> Let web pages specify their own fonts also doesn't have any effect because a default font is always used. let me know if i should open this up as a separate bug. see debian bug #478198 (http://bugs.debian.org/478198).
Just letting you know, that as of epiphany revision 8264 and WebKit-gtk r34271 I can successfully zoom in/out using the buttons in toolbar, entries in menu or ctrl-+/-. Zoom to normal size seems however to be disabled. It zoomes only text which is IMHO desired behaviour.
(In reply to comment #10) > Just letting you know, that as of epiphany revision 8264 and WebKit-gtk r34271 > I can successfully zoom in/out using the buttons in toolbar, entries in menu or > ctrl-+/-. Zoom to normal size seems however to be disabled. Fixed in r8281. > > It zoomes only text which is IMHO desired behaviour. > WebKit has API to enable full content zoom. If anyone wants to add preference UI or some way of optionally enabling that, I can review the patch in a new bug.
This is great! Thanks for the hard work on getting this feature implemented. I would recommend text-only zoom as the default. Full content zoom is a decent feature to have available, but it isn't very good as a default. I've seen firefox 3's full content zoom (which is their default) -- parts of the zoomed-in page usually end up outside the viewable window, and the images end up looking terrible.
i just tried epiphany-wekbit 2.24, and text resize still does not work. is this problem supposed to be fixed in this stable version or is it coming in 2.26?
Should be trunk only.
ok, thanks for the info. will this be pushed into the stable 2.26 release?