But are you planning to run test builds against live websites? That's
not very polite on people's servers (i certainly wouldn't like anyone
stress-testing my own servers for their benefit). And like some other
people said, tests that rely on network randomness are not very
reliable indicators
On Mon, Jan 23, 2012 at 2:14 AM, Aaron Boodman a...@google.com wrote:
On Sun, Jan 22, 2012 at 12:00 PM, Peter Kasting pkast...@google.com wrote:
On Sun, Jan 22, 2012 at 11:55 AM, Balazs Kelemen kbal...@webkit.org wrote:
As the goal is to test real world use case I think it can be even better
I don't think this needs to be done by every developer on every checkin. It
could be done by the buildbots daily, and whenever a crash is found, somebody
would need to find the cause and turn it into a real regression test for later.
The fact that the web sites change over time isn't
People run test builds against live servers by hand all the time. As long as
we don't do it too often, I don't see a problem. Especially as this list would
be taken from a list of top 100 web sites, which presumably would each be big
enough to handle the traffic.
-Original Message-
Hi All,
I'm seeing the commit-queue bot
http://webkit-commit-queue.appspot.com/queue-status/commit-queue/bots/ec2-cq-02
consistently rebooting about every hour. I know I'm not the only one with a
patch that has commit-queue+ waiting for this to be resolved.
Can someone look into this
On Mon, Jan 23, 2012 at 11:07 AM, Konrad Piascik kpias...@rim.com wrote:
I'm seeing the commit-queue bot
http://webkit-commit-queue.appspot.com/queue-status/commit-queue/bots/ec2-cq-02
consistently rebooting about every hour. I know I'm not the only one with a
patch that has commit-queue+
On Mon, Jan 23, 2012 at 11:12 AM, Adam Barth aba...@webkit.org wrote:
On Mon, Jan 23, 2012 at 11:07 AM, Konrad Piascik kpias...@rim.com wrote:
I'm seeing the commit-queue bot
http://webkit-commit-queue.appspot.com/queue-status/commit-queue/bots/ec2-cq-02
consistently rebooting about every
On 17/01/2012, at 10:41 AM, Bear Travis wrote:
A group of us at Adobe has been looking into adding support for
ProgressEvents
to images. The overall goal is to simplify image download progress reporting
by supporting roughly the same progress events as XHR and the File API for
image
Ok, I'm going to file a bug for style checker. And, add you guys to CC. :-)
Thank you,
Gyuyoung.
On Sat, Dec 31, 2011 at 7:09 AM, David Levin le...@google.com wrote:
Feel free to patch the style checker as appropriate. I suspect there may
be some changes needed here:
Hello Dave,
As I mentioned in previous email, I couldn't change the coding style of
public header file. So, EFL port still has naming violation regarding EFL
coding style in public header.
It also influences on .cpp files. For example, function naming, EFL data
type. So, I only could remove
In new port case, for example EFL port, we unfortunately don't have special
reviewer for our port yet.
So, we have requested to review on IRC after finishing our informal review.
If we only
ask some reviewers to review, the reviewers will have too many review
burden. We have
found proper reviewers
In new port case, for example EFL port, we unfortunately don't have special
reviewer for our port yet.
So, we have requested to review on IRC after finishing our informal review.
If we only
ask some reviewers to review, the reviewers will have too many review
burden. We have
found proper reviewers
Hello WebKit folks.
It looks that the result of layout test for EFL port needs rebaseline
because of 101343. The revision modified line spacing of font in
SimpleFontDataFreeType.cpp, and it seems that the existing layout test
result of EFL port was influenced by it. (
On Mon, Jan 16, 2012 at 12:02 AM, Gyuyoung Kim gyuyo...@gmail.com wrote:
Hello WebKit folks.
It looks that the result of layout test for EFL port needs rebaseline
because of 101343. The revision modified line spacing of font in
SimpleFontDataFreeType.cpp, and it seems that the existing
On 1/23/12 2:55 PM, Dean Jackson wrote:
On 17/01/2012, at 10:41 AM, Bear Travis wrote:
img id=image src=sample.jpg
onloadstart=showProgressBar()
onprogress=updateProgressBar(event)
onloadend=hideProgressBar()/
Developers have taken various tacks to enable progress reporting,
Hi Dean,
Thank you for the feedback. We have floated the idea to the WHATWG mailing
list, and are attempting to build enough support to draft a proper
proposal.
-Bear
On 1/23/12 2:55 PM, Dean Jackson d...@apple.com wrote:
On 17/01/2012, at 10:41 AM, Bear Travis wrote:
A group of us at
There's a brief discussion of the cross-origin case in the
ProgressEvents for Images WhatWG thread:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-January/034362.htm
l and the WebKit bug about this proposed feature:
https://bugs.webkit.org/show_bug.cgi?id=76102
For cross-site images for
On Mon, Jan 23, 2012 at 4:02 PM, Hans Muller hmul...@adobe.com wrote:
There's a brief discussion of the cross-origin case in the
ProgressEvents for Images WhatWG thread:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-January/034362.htm
l and the WebKit bug about this proposed
18 matches
Mail list logo
