Bug 44195 - [chromium] TilingData::tilePositionY has typo of X where Y should be used
Summary: [chromium] TilingData::tilePositionY has typo of X where Y should be used
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-18 12:18 PDT by Vincent Scheib
Modified: 2010-08-19 21:52 PDT (History)
3 users (show)

See Also:


Attachments
Patch (1.14 KB, patch)
2010-08-18 12:19 PDT, Vincent Scheib
no flags Details | Formatted Diff | Diff
Patch (8.53 KB, patch)
2010-08-19 17:31 PDT, Vincent Scheib
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Scheib 2010-08-18 12:18:37 PDT
[chromium] TilingData::tilePositionY has typo of X where Y should be used
Comment 1 Vincent Scheib 2010-08-18 12:19:30 PDT
Created attachment 64753 [details]
Patch
Comment 2 Vincent Scheib 2010-08-18 12:23:46 PDT
Single character typo from X to Y.
Comment 3 David Levin 2010-08-18 12:25:57 PDT
Comment on attachment 64753 [details]
Patch

Please either add a layout test to catch this OR
Mention which layout test covers it (in the ChangeLog) OR
Mention why it is impossible to add a layout test for this -- hopefully not -- (in the ChangeLog).
Comment 4 David Levin 2010-08-18 12:27:58 PDT
btw, the recursive nature of this call seems odd to me when a simple loop would avoid it.
Comment 5 Vincent Scheib 2010-08-18 14:36:10 PDT
Layout tests are not yet possible for this code for a few reasons:
- TilingData is currently only used behind a compile time flag as we develop GPU accelerated support for Canvas 2D. 
- TilingData is driven by a system GPU's maximum supported texture size, which varies on different hardware. We will need to plumb testing code that enables a layout test to supply a false value for GLES2Texture to mock as the maximium texture size at test time only.
Comment 6 David Levin 2010-08-19 08:34:40 PDT
(In reply to comment #5)
> Layout tests are not yet possible for this code for a few reasons:
> - TilingData is currently only used behind a compile time flag as we develop GPU accelerated support for Canvas 2D. 

Yes but a layout test could be written that would hit this code when the flag is flipped.

> - TilingData is driven by a system GPU's maximum supported texture size, which varies on different hardware. We will need to plumb testing code that enables a layout test to supply a false value for GLES2Texture to mock as the maximium texture size at test time only.

Is there a current typically upper bound? How hard would it be to hit that (or some large multiple of that) for the layout test?

Lastly, why is this method recursive when a loop could easily do the same thing?
Comment 7 Vincent Scheib 2010-08-19 17:31:10 PDT
Created attachment 64918 [details]
Patch
Comment 8 WebKit Commit Bot 2010-08-19 21:52:26 PDT
Comment on attachment 64918 [details]
Patch

Clearing flags on attachment: 64918

Committed r65726: <http://trac.webkit.org/changeset/65726>
Comment 9 WebKit Commit Bot 2010-08-19 21:52:31 PDT
All reviewed patches have been landed.  Closing bug.