On Thu, Mar 22, 2012 at 10:38 AM, Eric Seidel e...@webkit.org wrote:
Thank you. Mark Rowe was kind enough to resolve
https://bugs.webkit.org/show_bug.cgi?id=81838#c8 in
http://trac.webkit.org/changeset/111634.
I've found that some of the Weak External Symbol errors from
Hi,
As many of you may notice, we (as the WebKit team at RIM) are now more active
in contributing patches to WebKit.org. To move another step forward, we're in
preparation for bringing a build machine to WebKit.org to build our BlackBerry
port. I was reading this
Hi Ming,
I would be happy to help you out with this. Send me an email and we can
coordinate.
Lucas
On Mar 22, 2012, at 8:15 AM, Ming Xie wrote:
Hi,
As many of you may notice, we (as the WebKit team at RIM) are now more active
in contributing patches to WebKit.org. To move another step
Hi all,
I just wanted to give you an update and let you know that I checked in an
initial implementation of this feature yesterday! There was some concern about
enabling this everywhere while it's still a work in progress to avoid the
problem of any particular port accidentally shipping with a
I think that might have worked. :) Thanks.
On Thu, Mar 22, 2012 at 12:36 AM, Hajime Morrita morr...@chromium.org wrote:
On Thu, Mar 22, 2012 at 10:38 AM, Eric Seidel e...@webkit.org wrote:
Thank you. Mark Rowe was kind enough to resolve
https://bugs.webkit.org/show_bug.cgi?id=81838#c8 in
Going ahead with the land now.
Will be around for several hours fixing builds. I'm sorry for any breaks.
-eric
On Wed, Mar 21, 2012 at 7:08 PM, Eric Seidel e...@webkit.org wrote:
I've posted my first-draft patch to:
https://bugs.webkit.org/show_bug.cgi?id=81844
If port maintainers would
Resurrecting a really old thread so continue the conversation now that I'm
hitting this issue :).
On Mon, Aug 16, 2010 at 2:16 PM, Sam Weinig sam.wei...@gmail.com wrote:
I am not sure I agree. Does our behavior actually cause any real bugs in
the places you have tracked down? The log spam
The move appears to be a success.
Mac, CrMac, CrWin, CrLinux, Gtk and Qt are all back building again.
Win, CrAndroid and EFL are in progress.
HUGE thank you to Mark Rowe, Tony Chang, Jessie Berlin, Martin
Robinson, Csaba Osztrogonac, Carlos Garcia Campos, Michael Saboff, and
Filip Pizlo for all
I've recently been greening Chromium's expectations for css3/selectors3.
~10% of these test need interaction (e.g. hovering over a link or selecting
text). Given that this is an imported test suite does it make sense to add
the appropriate layoutTestController hooks? As it is, the tests aren't
On Thu, Mar 22, 2012 at 18:41, Ojan Vafai o...@chromium.org wrote:
I've recently been greening Chromium's expectations for css3/selectors3.
~10% of these test need interaction (e.g. hovering over a link or selecting
text). Given that this is an imported test suite does it make sense to add
the
On Thu, Mar 22, 2012 at 6:41 PM, Ojan Vafai o...@chromium.org wrote:
I've recently been greening Chromium's expectations for css3/selectors3.
~10% of these test need interaction (e.g. hovering over a link or selecting
text). Given that this is an imported test suite does it make sense to add
Hey Dave,
Can you describe the use case for this new property? When would an author use
it?
-Sam
On Mar 22, 2012, at 4:16 PM, David Levin le...@chromium.org wrote:
Resurrecting a really old thread so continue the conversation now that I'm
hitting this issue :).
On Mon, Aug 16, 2010 at
On Mar 22, 2012, at 6:41 PM, Ojan Vafai o...@chromium.org wrote:
I've recently been greening Chromium's expectations for css3/selectors3. ~10%
of these test need interaction (e.g. hovering over a link or selecting text).
Given that this is an imported test suite does it make sense to add
Suppose I am using a framework does window.frameElement for various
reasons. When that framework is used in an iframe, it causes errors to
appear in the console.
For example, suppose the framework does this:
var a;
try {
a = window.frameElement; // WebKit outputs a console error here.
if
On Sat, Mar 10, 2012 at 12:49 PM, Maciej Stachowiak m...@apple.com wrote:
I made a bad choice of survey site. They want to charge me to see more than
100 responses or to export the data, but they won't take my money. Sadness.
Please try this survey instead, it will run through the 17th.
The
I wonder if we could expose the parent document's origin, so you could
write the check as follows:
if (parent.location.origin != location.origin)
return;
It's slightly subtle because we wouldn't want to expose the origin of
child frames (then you could probe the redirect structure of private
16 matches
Mail list logo
