Hi,
I was wondering if we could remove the CUSTOM_PROTOCOLS compile guard?
I believe this is the default code path for all ports now since we moved EFL to
use it last week
https://bugs.webkit.org/show_bug.cgi?id=128177
At least, it is mandatory for GTK and EFL builds, I don't know much about
Hi again Andre
I am learning towards the assert being right. It appears sub-classes will be
placed on 64bit aligned address on Win x64. This breaks some assumptions on
how arrays are layed out. I will have to check where we make use if the
assumptions asserted here, and see how bad it is.
On Oct 14, 2014, at 3:25 AM, Pascal Jacquemart p.jacquem...@samsung.com
wrote:
At least, it is mandatory for GTK and EFL builds, I don't know much about
other ports
What file turns this on for GTK builds? I see it set in cmake/OptionsEfl.cmake
for the EFL port, and in
On Tue, Oct 14, 2014 at 9:29 AM, Darin Adler da...@apple.com wrote:
What file turns this on for GTK builds? I see it set in
cmake/OptionsEfl.cmake for the EFL port, and in WebKit2/WebKit2Prefix.h for
the Mac and iOS ports.
Like the Mac and iOS ports, this is enabled via
4 matches
Mail list logo