<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Two decimal digits are probably not enough to specify object position and size" href="https://bugs.documentfoundation.org/show_bug.cgi?id=44267#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Two decimal digits are probably not enough to specify object position and size" href="https://bugs.documentfoundation.org/show_bug.cgi?id=44267">bug 44267</a> from <a class="email" href="mailto:eyalroz@technion.ac.il" title="Eyal Rozenberg <eyalroz@technion.ac.il>"> Eyal Rozenberg</a> <pre>Coming from the recent dupe bug, I suggest this bug's name be changed from "probably" to "definitely". Just for comparison - remember that scanners typically support 2400 DPI resolution if not higher, which means 1 pixel is ~10^-6m = 0.001 cm. No reason why we should not be able to position content on a page at this resolution. (In reply to Lionel Elie Mamane from <a href="show_bug.cgi?id=44267#c12">comment #12</a>) > There, with advice from UX team, it was decided to > forcibly round to 10^-4 m (two decimal digits in cm) rather than display > full precision. With due respect to UX considerations - at the very least there should be an option controlling this. It is not reasonable to cripple an app just to make the fractional digits slightly less confusing to newbies. I understand that some underlying infrastructure is limited to 10^-5 meter increments, and the UX people might want to hide some semi-incoherent rounding artifacts at that resolution. If that's the case, then it's the underlying representation which should be made to use higher resolution.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>