<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Gtk] [Wayland] Epiphany fails to render DuckDuckGo pages"
href="https://bugs.webkit.org/show_bug.cgi?id=144544#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Gtk] [Wayland] Epiphany fails to render DuckDuckGo pages"
href="https://bugs.webkit.org/show_bug.cgi?id=144544">bug 144544</a>
from <span class="vcard"><a class="email" href="mailto:mrobinson@webkit.org" title="Martin Robinson <mrobinson@webkit.org>"> <span class="fn">Martin Robinson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=144544#c7">comment #7</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=144544#c6">comment #6</a>)
>
> > Do any important sites break without 3D CSS transforms? We already disable
> > WebGL in Epiphany, so that won't be a regression for us. I'm pretty sure
> > these three bugs are much more serious. I always prefer a proper fix to a
> > workaround and hate to disable all your work on accelerated compositing, but
> > if that fixes these issues we should absolutely do so.
>
> I think a better approach is to simply fix this bug than to disable
> anything. I don't think AC or hidpi are features that we can reasonably turn
> off.</span >
To expand on this, if hidpi support was added without considering accelerated compositing mode, the feature is incomplete and needs to be finished.</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>