No subject

oding". Is this no longer true?

> >   - get/set the total application cache maximum size;
>=20
> Cache sizes are calculated automatically depending on the cache model set:
>=20
> http://www.webkitgtk.org/reference/webkit2gtk/stable/WebKitWebContext.htm=
l#webkit-web-context-set-cache-model

Sounds good.

> >   - a comparable API to WebKitViewportAttributes;
> >   - access to the DOM of a page/frame;
>=20
> http://www.webkitgtk.org/reference/webkit2gtk/stable/WebKitWebPage.html#w=
ebkit-web-page-get-dom-document
>=20
> >   - the following properties:
> >     * on WebKitWebSettings:
> >       - auto-resize-window,

This behavior is annoying and it would be nice to be able to turn it off.

> >       - enable-universal-access-from-file-uris (ignorable if unsetting =
security policies is possible),
> >       - enable-file-access-from-file-uris (ignorable if unsetting secur=
ity policies is possible),

If functions to unset policies on schemes is added, these are unrequired, o=
therwise once you lock down the file scheme, you can't unlock it.

> >       - enable-display-of-insecure-content (there is only a signal that=
 it happened),
> >       - enable-running-of-insecure-content (same as display variant),

I suppose the policies also take care of these.

> >       - enable-scripts,

It would be nice to have really crude NoScript support.

> >       - enable-dom-paste,

Is javascript-can-access-clipboard a superset of this? If so, I can live wi=
th just that.

> >       - auto-shrink-images,
> >       - respect-image-orientation,

They exist in WebKit1 and users might want these behaviors.

> >       - enable-spatial-navigation,

I suppose this might be someone's preferred link navigation method=E2=80=A6=
 Personally, I just use a link labeller.

> >       - editing-behavior,

Maybe someone likes editing behavior other than "native"?

> >       - enforce-96-dpi,

This is under "hack" anyways, so this can disappear without qualms.

> >       - minimum-font-size,
> >       - minimum-logical-font-size,

WebKit2 is showing much smaller fonts than WebKit1 with the same settings; =
I'll have to do some investigating as to whether it's just a WebKit1 -> Web=
Kit2 change or these variables are helping WebKit1.

> >       - enable-accelerated-compositing (is this always true in WebKit2?=
),
> >       - enable-css-shaders,
> >       - enable-media-stream,

I'm guessing these are always enabled in WebKit2. I imagine they were optio=
nal because they were unstable. I'm fine with living without these.

> >     * on WebKitWebInspector:
> >       - javascript-profiling-enabled,
> >       - timeline-profiling-enabled,

The timeline-profiling-enabled property was already deprecated, but it'd be=
 nice to be able to control the inspector without a mouse (to click the but=
tons for these).

> >     * on WebKitWebView:
> >       - transparent,
> >       - editable.

These behaviors are really nice to have (I use editable at least).

> > If I'm missing something in WebKit2 that does the same thing, I may hav=
e missed it. I've been over both sets of docs a few times and still find ne=
w things every now and then. If there is no plans to support a feature, the=
 only ones which are 100% required for uzbl to work is access to the scroll=
bars, SoupSession, and page's JavaScript context.
>=20
> We need use cases for those, to understand the problems.

I don't really have hard use cases for all of them. A few are just "huh, wh=
ere'd that go?" when moving over to WebKit2. Uzbl is basically a browser wh=
ich tries to expose all WebKit settings to the user. In the end, it'd be ni=
ce to have all of these so that I can remove a lot of #ifndef USE_WEBKIT2 b=
locks from the code (or at least have #else sections for them).

[1]https://mail.gnome.org/archives/libsoup-list/2013-January/msg00001.html

--=20
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the assignee for the bug.=