[webkit-dev] webkitPostMessage

I'm trying to understand why we have both DOMWindow.webkitPostMessage and DOMWindow.postMessage. I'm also trying to understand the following comment in {JS,V8}DOMWindowCustom.cpp: // This function has variable arguments and can be: // Per current spec: // postMessage(message, target

Re: [webkit-dev] CSS 2.1 Test Suite

As we have previous discussed following https://lists.webkit.org/pipermail/webkit-dev/2012-March/019782.html, it's hard to judge whether a given reference result is enough to cover everything the test intends to test. e.g. you can have a bug such that both the test and the reference file ends up ha

[webkit-dev] CSS 2.1 Test Suite

Hi there, We currently add tests from the CSS 2.1 suite as we fix them. They get added to the css2.1/20110323 folder in LayoutTests. Most of them don't have native reference tests yet in the suite so we (mostly I) have been adding homebrew reference results to the folder to avoid generating pix

[webkit-dev] Updating Media Source implementation

Hi WebKit, I just wanted to let people know that I plan on updating the Media Source implementation to the new 0.4 spec. The updated spec is intended to address a variety of concerns people had with th

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

I agree with Ojan. It's clear that there are arguments for both approaches and my initial note did not address all the situations that come up. I will write up something further and put it on the wiki. I will also continue mulling over what sorts of changes to the tools we could do in the short te

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

On Tue, Apr 10, 2012 at 12:29 PM, Ojan Vafai wrote: > I don't think we can come up with a hard and fast rule given current > tooling. In a theoretical future world in which it's easy to get expected > results off the EWS bots (or some other infrastructure), it would be > reasonable to expect peop

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

I don't think we can come up with a hard and fast rule given current tooling. In a theoretical future world in which it's easy to get expected results off the EWS bots (or some other infrastructure), it would be reasonable to expect people to incorporate the correct expected results for any EWS-hav

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

On Tue, Apr 10, 2012 at 11:42 AM, Stephen Chenney wrote: > On Tue, Apr 10, 2012 at 1:00 PM, Ryosuke Niwa wrote: > >> On Tue, Apr 10, 2012 at 6:10 AM, Stephen Chenney >> wrote: >> >>> There is a significant practical problem to "turn the tree red and work >>> with someone to rebaseline the tests"

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

On Tue, Apr 10, 2012 at 6:10 AM, Stephen Chenney wrote: > There is a significant practical problem to "turn the tree red and work > with someone to rebaseline the tests". It takes multiple hours for some > bots to build and test a given patch. That means, at any moment, you will > have maybe tens

Re: [webkit-dev] handling failing tests (test_expectations, Skipped files, etc.)

There is a significant practical problem to "turn the tree red and work with someone to rebaseline the tests". It takes multiple hours for some bots to build and test a given patch. That means, at any moment, you will have maybe tens and in some cases hundreds of failing tests associated with some

Re: [webkit-dev] Marquee as overflow property's value

I think it might be because marquee is non-compliant HTML. To my knowledge, WebKit only supports marquee in a best-effort capacity for compatibility with old pages. It is only reasonable to expect that, until (or unless, since the module's been in CR since 2008) the CSS Marquees module matures,

Re: [webkit-dev] List of prefixed APIs in WebKit

While it'd require some archaeology, would it be useful to compile a list of formerly prefixed APIs which have graduated? -Tony On Sat, Apr 7, 2012 at 2:10 AM, Adam Barth wrote: > As you might be aware, there's been some amount of debate in the > browser community recently about the use of vend

[webkit-dev] Marquee as overflow property's value

Dear WebKit team, Could someone please elicit as to why marquee is added as one of the overflow style property's value? [See: RenderStyleConstants.h] *enum EOverflow { OVISIBLE, OHIDDEN, OSCROLL, OAUTO, OOVERLAY, OMARQUEE };* Because of this, while setting the style properties for a marquee