Bug Tracker

Changes between Initial Version and Version 1 of Ticket #7730, comment 7


Ignore:
Timestamp:
Dec 26, 2010, 7:29:31 PM (12 years ago)
Author:
snover
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7730, comment 7

    initial v1  
    1 So, if I’m understanding this issue correctly, the problem with parseInt for most browsers (which don’t do sub-pixel rendering) is that it doesn’t round—it just drops the fractional amount.
     1So, if I’m understanding this issue correctly, the problem with parseInt for most browsers is that it doesn’t round—it just drops the fractional amount—which means browsers that use round instead of floor when deciding how to place fractional pixels end up jumping.
    22
    3 Are there browsers that don’t report fractional amounts? If so, what might work as a reasonable test case would be to use a value that doesn’t round properly currently (like 1.7), set & get it, then Math.round and compare. Incorrect behaviour would end up with 1; correct behaviour would end up with 2. Right?
     3What might work as a reasonable test case would be to use a value that doesn’t round properly currently (like 1.7), set & get it, then Math.round and compare. Incorrect behaviour would end up with 1; correct behaviour would end up with 2. Right? Are there browsers that actually use floor behaviour?