On Dec 3, 2012, at 5:18 PM, Michael Nordman wrote:
> About MemCache considerations, you list these options...
> * Do not share storage
> * Share storage but hits in remote caches are asynchronous
> * Share storage and all cache hits are serviced synchronously
>
> Is there a fourth option?
> * S
About MemCache considerations, you list these options...
* Do not share storage
* Share storage but hits in remote caches are asynchronous
* Share storage and all cache hits are serviced synchronously
Is there a fourth option?
* Share storage and all cache hits are async in all cases (the resultin
I recently added touch based drag/drop for chromium in general (
https://bugs.webkit.org/show_bug.cgi?id=101545)
Note that except for the initiation of drag, webkit drag/drop
infrastructure does not depend on the device. So its mostly the embedder's
responsibility to provide the relevant drag-updat
There's been a somewhat fragmented discussion across webkit-dev and
various bugs about how we ought to approach multiprocess networking in
WebKit. In an attempt to organize my thoughts, I wrote up a short
design document that compares various approaches:
https://docs.google.com/document/d/1ihpwbi
>> On Mon, Dec 3, 2012 at 12:59 PM, Dirk Schulze wrote:
>> Depends on the future. But for such a small patch, a new flag seems to be
>> overdone. I looked into the patch, and adding the flag caused more code,
>> then the actual feature (even if the computed style is missing). I believe
>> we sh
On Dec 3, 2012, at 2:54 PM, Alexis Menard wrote:
>
> On Dec 3, 2012 6:21 PM, "Dirk Schulze" wrote:
> >
> >
> > On Dec 3, 2012, at 1:15 PM, Benjamin Poulain wrote:
> >
> > > On Mon, Dec 3, 2012 at 12:59 PM, Dirk Schulze wrote:
> > > Depends on the future. But for such a small patch, a new fla
On Dec 3, 2012 6:21 PM, "Dirk Schulze" wrote:
>
>
> On Dec 3, 2012, at 1:15 PM, Benjamin Poulain wrote:
>
> > On Mon, Dec 3, 2012 at 12:59 PM, Dirk Schulze
wrote:
> > Depends on the future. But for such a small patch, a new flag seems to
be overdone. I looked into the patch, and adding the flag
On Dec 3, 2012, at 1:15 PM, Benjamin Poulain wrote:
> On Mon, Dec 3, 2012 at 12:59 PM, Dirk Schulze wrote:
> Depends on the future. But for such a small patch, a new flag seems to be
> overdone. I looked into the patch, and adding the flag caused more code, then
> the actual feature (even if
On Mon, Dec 3, 2012 at 12:59 PM, Dirk Schulze wrote:
> Depends on the future. But for such a small patch, a new flag seems to be
> overdone. I looked into the patch, and adding the flag caused more code,
> then the actual feature (even if the computed style is missing). I believe
> we should remo
On Dec 3, 2012, at 12:07 PM, Benjamin Poulain wrote:
> On Mon, Dec 3, 2012 at 11:11 AM, Dirk Schulze wrote:
> Why does this feature have a flag at all? background-position with up to 4
> arguments is specified with CSS3 background and borders. There are three
> major implementations with this
On Mon, Dec 3, 2012 at 11:11 AM, Dirk Schulze wrote:
>
> Why does this feature have a flag at all? background-position with up to 4
> arguments is specified with CSS3 background and borders. There are three
> major implementations with this feature. So we are just catching up. If the
> future work
On Dec 3, 2012, at 8:43 AM, Simon Fraser wrote:
> On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
>
>> I plan to enable it by default on Qt and EFL ports this week. If
>> somebody wants me to enable it on their ports please tell me, I'll be
>> happy to do it.
>
> I think it's preferable to en
On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
> I plan to enable it by default on Qt and EFL ports this week. If
> somebody wants me to enable it on their ports please tell me, I'll be
> happy to do it.
I think it's preferable to enable for all ports if you think it's ready. In
general, featu
On Mon, Dec 3, 2012 at 12:08 PM, Dirk Schulze wrote:
>
> On Dec 3, 2012, at 6:12 AM, "Alexis Menard" wrote:
>
>> On Mon, Dec 3, 2012 at 10:42 AM, Dirk Schulze wrote:
>>>
>>> On Dec 3, 2012, at 5:31 AM, Alexis Menard wrote:
>>>
On Mon, Dec 3, 2012 at 10:19 AM, Dirk Schulze wrote:
>
>>>
On Dec 3, 2012, at 6:12 AM, "Alexis Menard" wrote:
> On Mon, Dec 3, 2012 at 10:42 AM, Dirk Schulze wrote:
>>
>> On Dec 3, 2012, at 5:31 AM, Alexis Menard wrote:
>>
>>> On Mon, Dec 3, 2012 at 10:19 AM, Dirk Schulze wrote:
On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
>>>
On Mon, Dec 3, 2012 at 10:42 AM, Dirk Schulze wrote:
>
> On Dec 3, 2012, at 5:31 AM, Alexis Menard wrote:
>
>> On Mon, Dec 3, 2012 at 10:19 AM, Dirk Schulze wrote:
>>>
>>> On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
>>>
Hi everyone,
I wanted to let you know that I have added
Thanks. I had a hunch that this would be the case.
Greets.
On Mon, Dec 3, 2012 at 2:55 PM, Žan Doberšek wrote:
> The 1.10 branch doesn't enable CSS3 flexbox support by default. To use
> -webkit-flex you have to recompile WebKitGTK+ with CSS3 flexbox enabled,
> i.e. passing --enable-css3-flexbox
The 1.10 branch doesn't enable CSS3 flexbox support by default. To use
-webkit-flex you have to recompile WebKitGTK+ with CSS3 flexbox enabled,
i.e. passing --enable-css3-flexbox to the configure script.
http://trac.webkit.org/browser/releases/WebKitGTK/webkit-1.10/configure.ac#L1010
http://trac.w
On Dec 3, 2012, at 5:31 AM, Alexis Menard wrote:
> On Mon, Dec 3, 2012 at 10:19 AM, Dirk Schulze wrote:
>>
>> On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
>>
>>> Hi everyone,
>>>
>>> I wanted to let you know that I have added the new CSS3
>>> background-position offsets support to WebKi
Hi Nagarjuna,Please mention what Visual studio you are using , which revision
of webkit you using as well?regardsrsadhu
> Date: Mon, 3 Dec 2012 17:21:48 +0530
> From: nagarjuna.atl...@gmail.com
> To: webkit-dev@lists.webkit.org
> Subject: [webkit-dev] [Build error]
>
> Hi all
>
> Build started:
On Mon, Dec 3, 2012 at 10:19 AM, Dirk Schulze wrote:
>
> On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
>
>> Hi everyone,
>>
>> I wanted to let you know that I have added the new CSS3
>> background-position offsets support to WebKit.
>>
>> This support is behind the ENABLE_CSS3_BACKGROUND featu
On Dec 3, 2012, at 4:51 AM, Alexis Menard wrote:
> Hi everyone,
>
> I wanted to let you know that I have added the new CSS3
> background-position offsets support to WebKit.
>
> This support is behind the ENABLE_CSS3_BACKGROUND feature define and
> it's disabled by default on all ports. I took
Hi everyone,
I wanted to let you know that I have added the new CSS3
background-position offsets support to WebKit.
This support is behind the ENABLE_CSS3_BACKGROUND feature define and
it's disabled by default on all ports. I took the conservative
approach despite it's a cool feature.
Long story
Hello.
For my development purposes I'm using the Gtk+ 3 port of WebKit (webkitgtk
1.10). I was trying to use 'display:-webkit-flex' feature which should be
available in webkit sources at least 7 months now as of changeset:117385
[1] which is a patch to bug 86529 [2]. But as it seems that this chan
24 matches
Mail list logo
