Re: [webkit-dev] EFL and GTK on Darwin

2014-02-11 Thread Alberto Garcia
On Mon, Feb 10, 2014 at 06:30:52PM -0800, Dan Bernstein wrote: 2. Is there a configuration of the GTK port that actually builds for Darwin? I have never tried it myself, but it works as far as I know, and there seems to be someone from Apple working on it:

Re: [webkit-dev] EFL and GTK on Darwin

2014-02-11 Thread Žan Doberšek
Hi. On Mon, Feb 10, 2014 at 6:30 PM, Dan Bernstein m...@apple.com wrote: Hi everyone, and especially EFL and GTK contributors! In preparation for changing PLATFORM(MAC) to be false when building for iOS, I have been reviewing usage of PLATFORM(MAC) throughout our codebase. Some of these

Re: [webkit-dev] EFL and GTK on Darwin

2014-02-11 Thread Dan Bernstein
On Feb 11, 2014, at 12:29 AM, Žan Doberšek zandober...@gmail.com wrote: Hi. On Mon, Feb 10, 2014 at 6:30 PM, Dan Bernstein m...@apple.com wrote: Hi everyone, and especially EFL and GTK contributors! In preparation for changing PLATFORM(MAC) to be false when building for iOS, I have

Re: [webkit-dev] On web-exposing features disabled at runtime

2014-02-11 Thread Manuel Rego Casasnovas
On Mon, 2014-02-10 at 13:38 -0800, Benjamin Poulain wrote: Can't we add a compile time flag instead? The chromium patch you linked is inelegant and it touches some hot paths. BTW, only with the compile flag the issue is not completely fixed. For example you can enable the compile flag but

Re: [webkit-dev] On web-exposing features disabled at runtime

2014-02-11 Thread Sergio Villar Senin
En 10/02/14 21:55, Maciej Stachowiak escribiu: The question is whether this is an acceptable behavior or not, and how to fix it in case we don't like it. I guess it's safe to conclude that it isn't something that we want in general, as it might confuse web authors (they see the how properties

Re: [webkit-dev] On web-exposing features disabled at runtime

2014-02-11 Thread Maciej Stachowiak
On Feb 10, 2014, at 1:38 PM, Benjamin Poulain benja...@webkit.org wrote: Can't we add a compile time flag instead? The chromium patch you linked is inelegant and it touches some hot paths. Another advantage of compile time flag is Andreas eventually notice when they become useless and

Re: [webkit-dev] On web-exposing features disabled at runtime

2014-02-11 Thread Benjamin Poulain
On 2/11/14, 9:26 AM, Maciej Stachowiak wrote: On Feb 10, 2014, at 1:38 PM, Benjamin Poulain benja...@webkit.org wrote: Can't we add a compile time flag instead? The chromium patch you linked is inelegant and it touches some hot paths. Another advantage of compile time flag is Andreas

Re: [webkit-dev] On web-exposing features disabled at runtime

2014-02-11 Thread Maciej Stachowiak
On Feb 11, 2014, at 10:25 AM, Benjamin Poulain benja...@webkit.org wrote: On 2/11/14, 9:26 AM, Maciej Stachowiak wrote: On Feb 10, 2014, at 1:38 PM, Benjamin Poulain benja...@webkit.org wrote: Can't we add a compile time flag instead? The chromium patch you linked is inelegant and it

[webkit-dev] Runtime flag for -webkit-sticky CSS Value

2014-02-11 Thread Myles C. Maxfield
Hello, WebKittens! I’m investigating the possibility of removing the runtime flag for the -webkit-sticky CSS value, which will turn on support for this for all ports. Are there any ports who depend on this runtime flag? The WebKit bug that introduced this runtime flag is