Summary: | getComputedStyle-transform.html accidentally relies on float formatting details | ||
---|---|---|---|
Product: | WebKit | Reporter: | Evan Martin <evan> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | darin, simon.fraser |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | OS X 10.5 | ||
Bug Depends on: | |||
Bug Blocks: | 18994 |
Description
Evan Martin
2009-10-08 16:41:48 PDT
I think the test should stay the same, but we should round when printing the output and comparing with the expected values. The strings in question look like "matrix(1, 0.36397, -0.842288, 1, 0, 0)" So are you suggesting parsing those strings into separate fields? Or can I read each field of the matrix as a float in js code, like by doing domnode.webKitTransform.<something here>? Oh, I think I found a better option: printf is actually specified to have this behavior (where trailing significant digits are chopped if they are 0). I think I can hack my float-printer to emulate it. (I still think the test is kinda wrong for the reason I mentioned though.) |