Bug 144938 - Writer table border styles offered are different in the toolbar button vs. Table Properties dialog
Summary: Writer table border styles offered are different in the toolbar button vs. Ta...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.0.4 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks: Writer-Tables
  Show dependency treegraph
 
Reported: 2021-10-05 09:53 UTC by Buovjaga
Modified: 2024-01-27 06:22 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot (39.56 KB, image/png)
2021-10-05 09:53 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Buovjaga 2021-10-05 09:53:59 UTC
Created attachment 175532 [details]
Screenshot

See screenshot which has the dropdowns side by side.
Comment 1 Buovjaga 2021-10-05 12:17:25 UTC
Samuel mentioned that this "now needs UX input on which should be preferred"
Comment 2 Heiko Tietze 2021-10-05 13:05:59 UTC
Appears to be not a difference but a limitation, see svtools/inc/borderline.hrc missing in TB from "Fine Dashed". But besides, any change requires in respect to the new border width?
Comment 3 Heiko Tietze 2021-10-07 13:11:21 UTC
Looking at the image it's unclear what the differences exactly are (the list could benefit from labels, but those could be too long). The preview is also hard to read in the running application.

And I wonder if the list is defined in ODF. In this case we have to obey.
Comment 4 Stéphane Guillou (stragu) 2022-01-26 12:45:38 UTC
Confirmed in:

Version: 7.3.0.2 / LibreOffice Community
Build ID: f1c9017ac60ecca268da7b1cf147b10e244b9b21
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

This makes it inconsistent for users, with no obvious reason why the two list should have different choices or a different order.
Comment 5 QA Administrators 2024-01-27 03:14:47 UTC
Dear Buovjaga,

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