On Wed, Dec 13, 2023 at 08:49:55PM -0700, Soren Stoutner wrote:
> Currently there is no real security support for Qt WebEngine in
> stable, which is an oversight that might surprise many Debian users.
> The purpose of this discussion is to figure out the best way to
> change that.
Hello,
I would
Control: tags -1 - wontfix + patch
On Mon, May 18, 2015 at 12:33:13PM +0100, Mark Hindley wrote:
> I have been bitten by this too: all of my webkit browsers crash with
> SIGILL since upgrading to Jessie on non SSE hardware.
I've been reproducing this, I think the solution is as easy as
disabling
On Mon, May 18, 2015 at 03:28:09PM +0100, Mark Hindley wrote:
> > I anyway wonder, what's the problem with the current code? Doesn't
> > the part inside #if USE(CF) || OS(UNIX) handle this already?
>
> I think the current code returns from the line
>
> return kCFBooleanTrue == canUseJIT.get();
On Mon, May 18, 2015 at 12:33:13PM +0100, Mark Hindley wrote:
> This patch at least fixes the environment variable so that
> JavaScriptCoreUseJIT=0 is honoured as a work-araound.
If this is not working properly then it should be fixed upstream.
You're using 2.4.x, right?
I anyway wonder, what's
On Sun, Feb 09, 2014 at 06:44:58PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> That being said, I would **love** to see Qt using the system
> webkit/whatever.
I don't see how this is even possible. WebKitGTK+ and WebKitQt are
not just API layers on top of WebCore (which is where the bulk
On Sat, Jul 05, 2008 at 09:32:36PM -0400, Michael Gilbert wrote:
> i would like to see the qt, gtk, and webkit.org webkit libraries
> merge at some point.
Regardless of whether this was ever feasible or not, both Qt and
Chromium have left the WebKit project, so I guess we can close this
bug?
Ber
6 matches
Mail list logo
