On Wed, Jul 18, 2012 at 9:53 PM, Benjamin Poulain benja...@webkit.org wrote:
On Wed, Jul 18, 2012 at 8:59 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
Though the W3C spec allows packing more than one touch point update in
a single touch event, it says nothing about how these updates should
be
Hi all,
Using commit-queue doesn't pardon a committer from causing build failures.
Notice that the commit queue only builds runs tests on Chromium Linux
port. Thus, any build failure that doesn't manifest itself on Chromium
Linux port — namely any JSC-specific or Windows/Mac specific build
(from the right address...)
Hi,
I don't think it is a reasonable expectation especially for non-chromium
developers.
It is possible for a change to break chromium-linux, chromium-win or
chromium-mac,
that means developers needs to have Linux, Mac and Windows machines to
ensure
the successful
On Thu, Jul 19, 2012 at 12:39 AM, Hajime Morrita morr...@chromium.orgwrote:
It is possible for a change to break chromium-linux, chromium-win or
chromium-mac,
that means developers needs to have Linux, Mac and Windows machines to
ensure
the successful build since there is no EWS for these
On Wednesday, July 18, 2012 12:53:35 PM ext Benjamin Poulain wrote:
On Wed, Jul 18, 2012 at 8:59 AM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
Though the W3C spec allows packing more than one touch point update in
a single touch event, it says nothing about how these updates should
be
It looks like this spec needs an update, not the WebKit tests.
I don't think the spec should be changed so that XInput based platforms cannot
satisfy the spec requirements. But I agree that the tests are good the way
they are because they enforce the requirement to at least possibly support
Hi,
What svn revision should I get if I want to compile a custom webkit
version on windows ?
Thanks
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
bugs.webkit.org is moving to our new hardware today at 5pm PDT. I apologize for
the short notice, but we had some last minute technical issues and weren't sure
we would be able to do it, but I also didn't want to postpone this until next
week. Downtime will be 1-2 hours.
If this timing is
Hello Webkitters!
The latest WD for WebIDL defines a supplemental interface of an interface A as
any element of the acyclic graph of interfaces that is connected to A through
implements statements or through the inheritance chain of another
supplemental interface:
Hi Andrei
I'm asking this because CSS Regions spec defines the Region interface as an
WebIDL supplemental interface that needs to be implemented by any object
that can be a region (Element, Pseudo elements etc.). Is there a way in
WebKit to write an interface that implements another as
http://build.webkit.org/waterfall?category=AppleWin
Windows release build
http://build.webkit.org/builders/Apple%20Win%20Release%20%28Build%29?numbuilds=50
Currently debug build is not working properly I guess...
Hope this helps
Pravin
On Thu, Jul 19, 2012 at 3:49 PM, foru...@smartmobili.com
Hey Kentaro,
On 7/19/12 6:20 PM, Kentaro Hara hara...@chromium.org wrote:
Hi Andrei
I'm asking this because CSS Regions spec defines the Region interface
as an
WebIDL supplemental interface that needs to be implemented by any object
that can be a region (Element, Pseudo elements etc.). Is
On Thu, Jul 19, 2012 at 9:29 AM, Andrei Bucur abu...@adobe.com wrote:
Hey Kentaro,
On 7/19/12 6:20 PM, Kentaro Hara hara...@chromium.org wrote:
Hi Andrei
I'm asking this because CSS Regions spec defines the Region interface
as an
WebIDL supplemental interface that needs to be
Hello Adam,
Sure: http://www.w3.org/TR/2012/WD-css3-regions-20120503/#the-region-interface
The spec does not explicitly states that the Region should be supplemental,
however after raising some issues on www-style (
http://lists.w3.org/Archives/Public/www-style/2012Jul/0251.html ) and talking
Hi WebKit,
I wanted to give you an update on the progress of the chromium-android
port. It's been almost a year since Andrei Popescu announced that we were
refactoring the Android port to be based on Chromium:
http://lists.webkit.org/pipermail/webkit-dev/2011-August/017738.html.
Since, then
What else can become a region besides an element? If there aren't too
many interfaces, we can just copy/paste this stanza into each IDL,
like we do for EventTarget. If there are a lot of them, then I agree
that you'll probably want a fancier Supplemental feature.
One way to approach that is to
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard alexis.men...@openbossa.org
wrote:
On Mon, Jul 9, 2012 at 6:53 PM, Brady Eidson beid...@apple.com wrote:
On Jul 9, 2012, at 2:43 PM, Alexis Menard
On 19.07.2012 19:53, Andreas Kling wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com
mailto:beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard
alexis.men...@openbossa.org mailto:alexis.men...@openbossa.org
wrote:
On Mon, Jul 9, 2012 at
On Jul 19, 2012, at 10:53 AM, Andreas Kling kl...@webkit.org wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard alexis.men...@openbossa.org
wrote:
On Mon, Jul 9, 2012 at 6:53 PM, Brady Eidson beid...@apple.com wrote:
On Thu, Jul 19, 2012 at 3:01 PM, Oliver Buchtala
oliver.bucht...@googlemail.com wrote:
On 19.07.2012 19:53, Andreas Kling wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard alexis.men...@openbossa.org
wrote:
On Mon,
Adam,
Currently, an Element is the only thing represented in the object model
that can become a CSS Region.
Pseudo-elements (::before and ::after) can become CSS Regions, but AFAIK
there isn't yet a representation of those in the OM. I'm hoping this
changes in the future (I'm working on a spec
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala oliver.bucht...@googlemail.com
wrote:
On 19.07.2012 19:53, Andreas Kling wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard alexis.men...@openbossa.org
wrote:
On Mon,
19.07.2012, 22:06, Alexis Menard alexis.men...@openbossa.org:
Say you have a low powered machine that can't link WebKit in debug
even stripped out of SVG etc...
... or you want to debug on device which cannot run debug WebKit under
gdb because of memory limit.
... or you want to print some
One reason for preferring printf syntax is that it results in dramatically more
compact code. In JSC we take advantage of this to have debug printf support
built even in release builds. So or example if you want CodeBlock to print
itself in a release build, you don't first have to #define a
On 19.07.2012 20:15, Brady Eidson wrote:
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala
oliver.bucht...@googlemail.com
mailto:oliver.bucht...@googlemail.com wrote:
On 19.07.2012 19:53, Andreas Kling wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala oliver.bucht...@googlemail.com
wrote:
Hi,
I am probably one of those people who much dislike printf-debugging.
What is your problem with using a debugger?
Maybe because the displayed information is not appropriate?
E.g., you would like
On Thu, Jul 19, 2012 at 7:20 PM, Filip Pizlo fpi...@apple.com wrote:
dataLog(foo %d bar %x baz %p\n, a, b, c);
Reasoning and valid arguments aside, that actually looks totally beautiful.
Do want.
-Kling
___
webkit-dev mailing list
I should note that WTF already has an API for this. See DataLog.h. In JSC we've
been using it quite extensively to add pretty printers for a bunch of classes.
-Filip
On Jul 19, 2012, at 11:03 AM, Brady Eidson beid...@apple.com wrote:
On Jul 19, 2012, at 10:53 AM, Andreas Kling
On 19.07.2012 20:26, Maciej Stachowiak wrote:
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala oliver.bucht...@googlemail.com
wrote:
Hi,
I am probably one of those people who much dislike printf-debugging.
What is your problem with using a debugger?
Maybe because the displayed information is
On Thu, Jul 19, 2012 at 3:20 PM, Filip Pizlo fpi...@apple.com wrote:
One reason for preferring printf syntax is that it results in dramatically
more compact code. In JSC we take advantage of this to have debug printf
support built even in release builds. So or example if you want CodeBlock to
On Thu, Jul 19, 2012 at 11:15 AM, Brady Eidson beid...@apple.com wrote:
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala
oliver.bucht...@googlemail.com wrote:
On 19.07.2012 19:53, Andreas Kling wrote:
On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012,
On Thu, Jul 19, 2012 at 11:35 AM, Oliver Buchtala
oliver.bucht...@googlemail.com wrote:
On 19.07.2012 20:26, Maciej Stachowiak wrote:
On Jul 19, 2012, at 11:01 AM, Oliver Buchtala
oliver.buchtala@googlemail.**com oliver.bucht...@googlemail.com wrote:
FWIW, there is a gdb python API for
But I do want a debugging utility to does land, is always compiled in, and that
everyone enjoys using.
-Filip
On Jul 19, 2012, at 11:37 AM, Alexis Menard alexis.men...@openbossa.org wrote:
On Thu, Jul 19, 2012 at 3:20 PM, Filip Pizlo fpi...@apple.com wrote:
One reason for preferring printf
On Thu, Jul 19, 2012 at 4:11 PM, Filip Pizlo fpi...@apple.com wrote:
But I do want a debugging utility to does land, is always compiled in, and
that everyone enjoys using.
The header itself in the patch would land so you can use it right away
(and compile even in release). But the actual
It sounds like you don't have a problem today, but you might have a
problem in the future. I'd recommend going with the simple solution
today and worrying about future problems in the future.
Adam
On Thu, Jul 19, 2012 at 11:04 AM, Alan Stearns stea...@adobe.com wrote:
Adam,
Currently, an
On Jul 19, 2012, at 2:28 AM, wingoog moon wingoo...@gmail.com wrote:
Hi all.
I'm trying to understand how resolve_global instruction works for several
days. Let's look at the code
void JIT::emit_op_resolve_global(Instruction* currentInstruction, bool)
{
// Fast case
void*
On Jul 10, 2012, at 8:52 AM, Brady Eidson beid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menard alexis.men...@openbossa.org
wrote:
On Mon, Jul 9, 2012 at 6:53 PM, Brady Eidson beid...@apple.com wrote:
On Jul 9, 2012, at 2:43 PM, Alexis Menard alexis.men...@openbossa.org
On Jul 19, 2012, at 2:46 PM, Antti Koivisto akoivi...@gmail.com wrote:
Maciej Stachowiak m...@apple.com kirjoitti 20.7.2012 kello 0.27:
In principle, we could also have this support multiple arguments, so you
could write:
debug(frame: , someFrame, node: , someNode, string,
On 07/19/2012 11:27 PM, Maciej Stachowiak wrote:
On Jul 10, 2012, at 8:52 AM, Brady Eidsonbeid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menardalexis.men...@openbossa.org wrote:
On Mon, Jul 9, 2012 at 6:53 PM, Brady Eidsonbeid...@apple.com wrote:
On Jul 9, 2012, at 2:43 PM,
On Jul 19, 2012, at 2:58 PM, Balazs Kelemen kbal...@webkit.org wrote:
On 07/19/2012 11:27 PM, Maciej Stachowiak wrote:
On Jul 10, 2012, at 8:52 AM, Brady Eidsonbeid...@apple.com wrote:
On Jul 10, 2012, at 5:25 AM, Alexis Menardalexis.men...@openbossa.org
wrote:
On Mon, Jul 9, 2012 at
On Jul 19, 2012, at 3:09 PM, Filip Pizlo fpi...@apple.com wrote:
On Jul 19, 2012, at 2:58 PM, Balazs Kelemen kbal...@webkit.org wrote:
But neither these compile to a single function call. Or we could define
simple inline debug() overrides but we could also do that with the stream
Hi webkit folks,
I can't aceess bugs.webkit.org now. It looks bugzilla system is not working
correctly. Is bugzilla dead ?
Gyuyoung.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
See my earlier email about the migration.
-Bill
On Jul 19, 2012, at 6:31 PM, Gyuyoung Kim gyuyoung@samsung.com wrote:
Hi webkit folks,
I can't aceess bugs.webkit.org now. It looks bugzilla system is not working
correctly. Is bugzilla dead ?
Gyuyoung.
The notification was sent when I was sleeping. I read it now.
Thanks,
Gyuyoung.
-Original Message-
From: William Siegrist [mailto:wsiegr...@apple.com]
Sent: Friday, July 20, 2012 10:36 AM
To: gyuyoung@samsung.com
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Is
On Jul 19, 2012, at 7:25 AM, William Siegrist wsiegr...@apple.com wrote:
bugs.webkit.org is moving to our new hardware today at 5pm PDT. I apologize
for the short notice, but we had some last minute technical issues and
weren't sure we would be able to do it, but I also didn't want to
If it weren't too much trouble, it might be nice to show some kind of
under maintenance page in the future so that we know for sure it's due to
the migration instead of migration-related outage.
- Ryosuke
On Thu, Jul 19, 2012 at 6:36 PM, William Siegrist wsiegr...@apple.comwrote:
See my
I think the notice was simply lost in all the bike-shedding of late. :)
Thank you Bill for taking care of the migration. I saw and
appreciated your email notice earlier.
-eric
On Thu, Jul 19, 2012 at 7:00 PM, Ryosuke Niwa rn...@webkit.org wrote:
If it weren't too much trouble, it might be
Yeah a maintenance page would be nice, but usually these outages aren't so
long. I did have a 503 on the old server for the first DB move. The need to
re-do the DB migration made this a lot messier then it should have been since
it happened after the DNS change. I like to be paranoid and leave
On Jul 19, 2012, at 6:59 PM, William Siegrist wsiegr...@apple.com wrote:
On Jul 19, 2012, at 7:25 AM, William Siegrist wsiegr...@apple.com wrote:
bugs.webkit.org is moving to our new hardware today at 5pm PDT. I apologize
for the short notice, but we had some last minute technical issues
49 matches
Mail list logo
