| Summary: | Confusing UX for Cell Navigation / Moving Image if Image Selected in Cell | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Freddie O’Connell <tfo> |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | trivial | CC: | buzea.bogdan, heiko.tietze, xiscofauli |
| Priority: | lowest | ||
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=125938 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 105584 | ||
| Attachments: |
Video of Cell Navigation
Test Spreadsheet |
||
|
Description
Freddie O’Connell
2019-08-13 22:14:16 UTC
Created attachment 153365 [details]
Video of Cell Navigation
This shows the behavior of standard cell navigation and then the strange trap if an image is selected.
@Freddie : any chance of a test spreadsheet with which I can attempt to reproduce ? Am wondering whether this is linked to the anchoring of the image...cf. bug 125938 (In reply to Alex Thurgood from comment #2) > @Freddie : any chance of a test spreadsheet with which I can attempt to > reproduce ? Me also cannot reproduce. Created attachment 153442 [details]
Test Spreadsheet
I am able to consistently reproduce the behavior in the video with this spreadsheet.
What you mean is the positioning with (wide) columns, and the effect of readjustment when this image is moved. One pixel more or less makes it fit together with column D or not (and admittedly the issue is in one step being recalculated falsely). (For those who don't want to load the file: col D take s75% of the width, the image in E ~25% and when moving the image to the right, the horizontal scrollbar jumps by showing col D or not in one step.) I would treat this as a bug (removing UX) but it's such a corner case that accepting this shortcoming is acceptable to me. [Automated Action] NeedInfo-To-Unconfirmed Dear Freddie O’Connell, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug |