Date: prev next · Thread: first prev next last
July 2020 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=134930

Mike Kaganski <mikekaganski@hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
           Keywords|needsUXEval                 |regression

--- Comment #10 from Mike Kaganski <mikekaganski@hotmail.com> ---
This is a regression.

In v.3.3, the field was read-only (although selectable). It didn't allow
changing its value directly (neither by typing, nor by using mouse wheel, arrow
keys, or PgUp/PgDn). Note that using wheel when mouse pointer was over that
field, but keyboard cursor was in a column width field (with "Adapt table
width" checked), looked as if it changed the remaining size, but actually
changed it only indirectly via changing the active column width.

In v.5.4, it also didn't accept typing - but it accepted arrow keys, PgUp/PgDn,
and wheel.

In current version (7.0.0.2) it now has spin buttons, and accepts typing.

All that direct input is not handled in code, and is of course wrong. It must
be read-only, just as e.g. old About dialog's data (selectable, but not
directly modifiable).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.