Hi,
So it seems WebKit2GTK+ builds are broken since yesterday due to this commit
(as it was already predicted by EWS in [1]):
http://trac.webkit.org/changeset/140285
... and it seems to me it's not something easily fixable since it will
certainly require a certain amount of work (and maybe a
On Mon, Jan 21, 2013 at 2:53 PM, Mario Sanchez Prada
mario.pr...@samsung.com wrote:
Hi,
(...)
If anyone could drop some light on this issue or provide some pointers to
better understand the motivation of this change, I’d really appreciate that.
I understand rolling r140285 might be not the
On Mon, 2013-01-21 at 15:27 +0100, Xan Lopez wrote:
On Mon, Jan 21, 2013 at 2:53 PM, Mario Sanchez Prada
mario.pr...@samsung.com wrote:
Hi,
(...)
If anyone could drop some light on this issue or provide some pointers to
better understand the motivation of this change, I’d really
Hi,
In WebKit both RGBA and BGRA formats are used for different purposes and
different platforms in WebKit. Do we have a policy which one we prefer? It
would be nice to reduce conversions between them in the future as it seems
costly on embedded systems.
Regards,
Zoltan
Hi
Building WebKit on a MacPro 5,1 (mid 2010 - 2.8GHz quad core Xeon with
SSD, 20 gb of ram, gigabit LAN) with Mac OS 10.8 takes 30 minutes and it
really slows down the daily work.
Buying new Macs is just too expensive and the current ones have plenty of
computing power if we use them to the
On Mon, Jan 21, 2013 at 1:41 PM, Mihai Maerean mmaer...@adobe.com wrote:
Hi
Hi,
Building WebKit on a MacPro 5,1 (mid 2010 - 2.8GHz quad core Xeon with
SSD, 20 gb of ram, gigabit LAN) with Mac OS 10.8 takes 30 minutes and it
really slows down the daily work.
Buying new Macs is just too
Hi,
On Mon, Jan 21, 2013 at 5:53 PM, Alexis Menard ale...@webkit.org wrote:
On Mon, Jan 21, 2013 at 1:41 PM, Mihai Maerean mmaer...@adobe.com wrote:
How can the build of WebKit be distributed on all the Macs in the LAN to
fully utilize the computing power?
Some folks have pointed out to me off thread that I'm coming off as
angry and harsh. I would like to apologize for my tone.
My goal here is not to obstruct or block your progress on the
NetworkProcess. My goal is to end up with a common design that we can
share between WebKit2 and Chromium or
On Sun, Jan 20, 2013 at 9:55 PM, TAMURA, Kent tk...@chromium.org wrote:
Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship input
type=datetimeimplementation in your products.
We had some discussion in WHATWG [1] [2] and realized input type=datetime
UIs in iOS Safari and Android Chrome
On Jan 20, 2013, at 9:55 PM, TAMURA, Kent tk...@chromium.org wrote:
Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship input
type=datetimeimplementation in your products.
What do you recommend for products that have shipped it already?
- Maciej
On Mon, Jan 21, 2013 at 7:00 AM, Zoltan Herczeg zherc...@webkit.org wrote:
In WebKit both RGBA and BGRA formats are used for different purposes and
different platforms in WebKit. Do we have a policy which one we prefer? It
would be nice to reduce conversions between them in the future as it
On Jan 21, 2013, at 11:23 AM, Adam Barth aba...@webkit.org wrote:
Some folks have pointed out to me off thread that I'm coming off as
angry and harsh. I would like to apologize for my tone.
My goal here is not to obstruct or block your progress on the
NetworkProcess. My goal is to end up
On Sat, Jan 12, 2013 at 9:49 PM, Nico Weber tha...@chromium.org wrote:
On Tue, Dec 11, 2012 at 3:43 PM, Eric Seidel e...@webkit.org wrote:
Nevermind. After further discussion with Nico, this can't work yet.
Ninja is currently configured to use a non-webkitty out build
directory, which is
Thank you Alexis-san, Dominic-san, Ryosuke-san
for guiding me gently.
I learned the custom and what this list is used for.
And, thank you Kent-san for assigning to me.
I'll do my best.
Many thanks,
高尾 将康
___
webkit-dev mailing list
Hi Mario,
The motivation of the change was to reduce the chatter between the WebProcess
and UIProcess and reduce the amount of knowledge the UIProcess has about the
internals of the WebProcess. We will also be removing the UIProcess' notion of
the frame tree, for the same reason.
Going
Please do not enable ENABLE_INPUT_TYPE_DATETIME to ship input
type=datetimeimplementation in your products.
What do you recommend for products that have shipped it already?
I recommend to disable it in the next release of the products. I'll
disable it for Android Chrome.
It's an
16 matches
Mail list logo
