On Tue, Apr 5, 2011 at 7:10 PM, Adam Roben aro...@apple.com wrote:
The best way to report a bug like this is to file a new bug at
http://webkit.org/new-bug. In this case, this is a known issue
(http://webkit.org/b/52913), so you don't need to do anything. There isn't
a workaround at this
On Apr 6, 2011, at 12:25 PM, Pere Martir wrote:
On Tue, Apr 5, 2011 at 7:10 PM, Adam Roben aro...@apple.com wrote:
The best way to report a bug like this is to file a new bug at
http://webkit.org/new-bug. In this case, this is a known issue
(http://webkit.org/b/52913), so you don't need to
64-bit Window 7.
run-webkit-tests reported that many tests crashed, in addition to many
other failures due to the metric difference.
Command line:
Tools/Scripts/run-webkit-tests compositing/iframes
Tests that caused DumpRenderTree tool to crash:
On Apr 5, 2011, at 1:02 PM, Pere Martir wrote:
64-bit Window 7.
run-webkit-tests reported that many tests crashed, in addition to many
other failures due to the metric difference.
Command line:
Tools/Scripts/run-webkit-tests compositing/iframes
Tests that caused DumpRenderTree tool
On Tue, Apr 5, 2011 at 7:10 PM, Adam Roben aro...@apple.com wrote:
The best way to report a bug like this is to file a new bug at
http://webkit.org/new-bug. In this case, this is a known issue
(http://webkit.org/b/52913), so you don't need to do anything. There isn't
a workaround at this
On Apr 5, 2011, at 1:17 PM, Pere Martir wrote:
On Tue, Apr 5, 2011 at 7:10 PM, Adam Roben aro...@apple.com wrote:
The best way to report a bug like this is to file a new bug at
http://webkit.org/new-bug. In this case, this is a known issue
(http://webkit.org/b/52913), so you don't need to
6 matches
Mail list logo
