[Bug 158624] text file format dialogue on save -- ODF file format?

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158624 --- Comment #3 from Heiko Tietze --- Whether the extension is ODT or ODS both are ODF. I see no benefit in a more specific wording like "Use the default ODS text file format to be sure..." or "Use the default ODS spreadsheet file format

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #7 from ady --- (In reply to Heiko Tietze from comment #6) > See my bug 91415 comment 6. And don't forget about bug 153106. Carefully written words, never read with the required attention. So, here we are. Am I surprised?

[Bug 158707] Double click on a comment in Navigator should open the cell for editing

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158707 --- Comment #3 from Heiko Tietze --- (In reply to Heiko Tietze from bug 158514 comment 4) > Bug 64701 asks for "Show Comments Should Select Comment for Editing" and I > wonder if double clicking the Navigator should not only select the

[Bug 135063] Calc column width auto fit not working when selection active outside column

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135063 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda

[Bug 158545] UI: Original size button in image properties -> position and size tab doesn't restore original size for paper size exceeding images in Writer (and breaks image ratio)

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158545 --- Comment #2 from Heiko Tietze --- Agree, the ratio should be kept. But what could be an alternative label for the original size? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 158689] Calc's double-click on column header boundary always uses the default +2 mm for optimal width, instead of what is defined in Format>Columns>Optimal Width

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158689 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval |needsDevEval

[Bug 158653] Comment commands in Calc's menus need to be rearranged

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug 158707] Double click on a comment in Navigator should open the cell for editing

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158707 --- Comment #4 from Heiko Tietze --- Double-checked with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b72aa31d7db38c81f757206e4e51844b839797ea CPU threads: 16; OS: Windows 10.0 Build 22000; UI render:

[Bug 158682] Calc: Move rows with protected cells does not give warning

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158682 --- Comment #2 from Heiko Tietze --- Or we don't copy neither show the copying rectangle on moving the row. Too many warnings spoil the broth. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 158940] Nomenclature: "Area" commands not homogeneous in UI for Writer Sections

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158940 --- Comment #3 from sophie --- I think any time the meaning is "background", it should be used instead of "area". "Area" should be used only when it has a meaning of "zone" or "region". -- You are receiving this mail because: You are

[Bug 158940] Nomenclature: "Area" commands not homogeneous in UI for Writer Sections

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158940 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|NEW

[Bug 127054] Whitespace is not Hidden if Column Breaks are Used

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127054 Heiko Tietze changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from

[Bug 127054] Whitespace is not Hidden if Column Breaks are Used

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127054 --- Comment #6 from Dieter --- Created attachment 191692 --> https://bugs.documentfoundation.org/attachment.cgi?id=191692=edit sample document after first 6 steps from comment 0 Steps: 1. Open attachment 2. Hide whitespace -- You

[Bug 158864] Many/most dark mode UI elements have too strong a contrast

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158864 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Blocks|

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 Heiko Tietze changed: What|Removed |Added Blocks||101216 See Also|

[Bug 91415] Improve design of comment indicators to block less of the cell's content

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91415 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda

[Bug 158940] Nomenclature: "Area" commands not homogeneous in UI for Writer Sections

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158940 Heiko Tietze changed: What|Removed |Added Blocks||115596, 113969

[Bug 127054] Whitespace is not Hidden if Column Breaks are Used

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127054 --- Comment #7 from Heiko Tietze --- (In reply to Harald Koester from comment #0) > [7] Hide whitespace Top and bottom areas are not displayed. > Expected: Only first line of page 1 should be displayed. This would be > equivalent,

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org ---

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #9 from ady --- (In reply to V Stuart Foote from comment #8) > No, bug 153106 was closed => WF for the reversion of the marker, with > expectation there would be an UNO enhancement ticket to control the Comment > indicator

[Bug 158682] Calc: Move rows with protected cells does not give warning

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158682 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Heiko Tietze from comment #2) > Or we don't copy neither show the copying rectangle on moving the row. Too > many warnings spoil the broth. I think this silence could seem

[Bug 158545] UI: Original size button in image properties -> position and size tab doesn't restore original size for paper size exceeding images in Writer (and breaks image ratio)

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158545 --- Comment #3 from Eyal Rozenberg --- I would have liked to say that original size should really mean the original size; but - at the moment, it seems Writer forbids exceeding page dimensions, so that might be impossible. Anyway,

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #10 from inso...@yandex.ru --- I think we should assume that the data is primary. The comment indicator should in no case interfere with the data at any viewing scale. I think a better option would be to give the user the

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #11 from V Stuart Foote --- (In reply to ady from comment #9) Yes it does make your objections invalid--UX decision was made for bug 153106 and a revert of the bug 91415 zoom responsive triangle marking for comments remains,

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #12 from V Stuart Foote --- (In reply to insonus from comment #10) Believe the current zoom responsive triangle marker is already drawn behind the cell's data values. The cells values are visible and not obscured, though

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #13 from inso...@yandex.ru --- Yes, marker is drawn behind the cell's data values, the cells values are visible. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 158784] Enable independent inheritance of “Spacing above” and “Spacing below” for paragraph styles

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158784 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||107833

[Bug 158958] Comment marker makes it difficult to see the data in a cell

2024-01-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158958 --- Comment #14 from ady --- (In reply to V Stuart Foote from comment #11) > (In reply to ady from comment #9) > > Yes it does make your objections invalid--UX decision was made for bug > 153106 and a revert of the bug 91415 zoom