Bug 81749 - [chromium] ScrollbarLayerChromiumTest.resolveScrollLayerPointer failing on Lion
Summary: [chromium] ScrollbarLayerChromiumTest.resolveScrollLayerPointer failing on Lion
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Keishi Hattori
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 02:31 PDT by Keishi Hattori
Modified: 2013-04-15 06:35 PDT (History)
7 users (show)

See Also:

Attachments
Patch (1.34 KB, patch)
2012-03-21 02:37 PDT, Keishi Hattori 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Keishi Hattori 2012-03-21 02:31:34 PDT 
ScrollbarLayerChromiumTest.resolveScrollLayerPointer failing on Lion
Comment 1 Keishi Hattori 2012-03-21 02:37:47 PDT 
Created attachment 132998 [details]
Patch
Comment 2 Ryosuke Niwa 2012-03-21 22:12:46 PDT 
Comment on attachment 132998 [details]
Patch

There's no way to test this?
Comment 3 James Robinson 2012-03-22 14:57:24 PDT 
Comment on attachment 132998 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=132998&action=review

Oh! That is a somewhat embarrassing bug.

Ryosuke - we do have a test for this (although it's not very direct) and it's failing currently.

> Source/WebCore/ChangeLog:6
> +        Reviewed by NOBODY (OOPS!).

would you mind documenting the test that this fixes (I believe it only impacts Lion since we force non-overlay scrollbars in tests on Snow Leopard, and I suppose that isn't true on Lion).
Comment 4 Ryosuke Niwa 2012-03-22 15:06:21 PDT 
(In reply to comment #3)
> (From update of attachment 132998 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=132998&action=review
> 
> Oh! That is a somewhat embarrassing bug.
> 
> Ryosuke - we do have a test for this (although it's not very direct) and it's failing currently.

That's good to know. Does the test pass after this change?