<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Copy&paste error in WKPreferencesSetMetaRefreshEnabled() and ...Get..."
href="https://bugs.webkit.org/show_bug.cgi?id=155352#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Copy&paste error in WKPreferencesSetMetaRefreshEnabled() and ...Get..."
href="https://bugs.webkit.org/show_bug.cgi?id=155352">bug 155352</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=155352#c3">comment #3</a>)
<span class="quote">> Yup, it's weird. I was looking for a way to disable http-equiv processing as
> such (my concern was about Content-Type with charset specified), when I
> noticed this "incompatibility". The name doesn't reflect what the function
> does, especially when there is another setting where one can do the same,
> with correct naming.</span >
My guess is that the old method was kept to not break the API.
<span class="quote">> I'd prefer to have this http-equiv disablement as a public option, easily
> accessible, ideally from the WebKitSettings or similar place. If you think
> it makes sense, I'll be happy to file a feature request for it.</span >
Yes, we don't use the WebKit2 C API in the GTK+ port, so if you need that setting (or any other) that is not exposed in WebKitSettings, just file a bug report explaining your use case to the GTK+ port.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>