Ojan,
As Simon states, some repaint tests will likely not be possible to write
correctly as ref tests, but some of them I think they fit very well in the
happy-no-pixel-test bucket :). If people decide it's a direction worth
investigating, I'll give the idea a spin.
Simon,
On Fri, May 25, 2012 a
On May 24, 2012, at 3:59 PM, Andrei Bucur wrote:
> No, I need a way to force a paint operation, similar to what
> layoutTestController.display() achieves, but without tracking the paint
> rectangles.
>
> Does anyone you find value in adding an optional parameter to display (or
> create another
Hello WebKit community,
We want to announce the W3C event "Test the Web Forward" hosted by Adobe. This
hackathon builds off the Move the Web Forward initiative in order to help get
developers more involved in contributing to the web platform we all work to
define.
During this hackathon, attend
On Thu, May 24, 2012 at 3:59 PM, Andrei Bucur wrote:
> No, I need a way to force a paint operation, similar to what
> layoutTestController.display() achieves, but without tracking the paint
> rectangles.
>
> Does anyone you find value in adding an optional parameter to display (or
> create another
No, I need a way to force a paint operation, similar to what
layoutTestController.display() achieves, but without tracking the paint
rectangles.
Does anyone you find value in adding an optional parameter to display (or
create another method on LTC) that disables paint rectangle tracking.
The main
Do you just need to force a layout at the end of repaintTest, e.g.
document.body.offsetHeight;?
On Thu, May 24, 2012 at 6:34 AM, Andrei Bucur wrote:
> Hello WebKittens,
>
> I'm trying to simplify the patch for a certain repaint bug (
> https://bugs.webkit.org/show_bug.cgi?id=59863 ) by using ref
> I think it would be great to talk about this at the WebKit summit
tomorrow, if you are there.
Unfortunately I wasn't able to make the WebKit summit, but beverloo
mentioned that you were able to chat a little. I'm happy to discuss further
by email or otherwise :)
For those who aren't following t
You should start following the accelerated_compositing macro
Also reading these might help
http://dev.chromium.org/developers/design-documents/gpu-accelerated-compositing-in-chrome
http://qtwebkit.blogspot.in/2010/10/texture-mapper-accelerated-compositing.html
http://trac.webkit.org/wiki/Accelerate
Hello WebKittens,
I'm trying to simplify the patch for a certain repaint bug (
https://bugs.webkit.org/show_bug.cgi?id=59863 ) by using ref tests instead
of pixel tests.
The test HTML file should first render the document in state 1 and then, by
modifying the DOM, render it again state 2. The bug
Hello,
Webkit has two rendering path, software rendering and hardware rendering. When
hardware rendering is enabled, it takes the hardware rendering path.
I would like to go through the code in the WebCore where it takes the decision
to go to either one of the path. As I am very new in using web
10 matches
Mail list logo