Scott Miles wrote: > This is a thorny problem, but my initial reaction is that you > threaded the needle appropriately. I don't see how we avoid some > lossiness in this situation.
Note that if you're using offsetWith/Height/Top/Bottom you already lose, because they return integers.
I think we should be doing what we can to discourage use of these broken APIs, for what it's worth, instead of worrying how we can extend their already-incorrect behavior to cover more cases "well".
-Boris
