[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5739 --- Comment #21 from Heiko Tietze --- We discussed the topic in the design meeting. Some complex configurations make the column sizing per dialog indeed weird. Since manual column sizing still works as expected we recommend to investigate the situation and aim for this behavior. For a full redesign idea see bug 145739. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #20 from Danat --- (In reply to Eyal Rozenberg from comment #19) > (In reply to Danat from comment #17) > > This is a simplified example > > FYI: I already created a simplified example. Your "sample file simplified" > and my "simplified reproducer" are almost identical. I see. I still maintain that the wisest way out here would be to tie it to the selection of cells. When you select cells and change column width in a column with a split cell - it affects only first cell. It is easy to tweak it so it affects all selected cells -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #19 from Eyal Rozenberg --- (In reply to Danat from comment #17) > This is a simplified example FYI: I already created a simplified example. Your "sample file simplified" and my "simplified reproducer" are almost identical. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval --- Comment #18 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #13) > Don't see how we should deal with issues from one badly designed file. This bug is not about the design of one file, but about LO behavior on a column with a split cell. Cell splitting is a legitimate feature to use and we can't just say that if someone split a cell then they have made "bad design" and the app can just act capriciously. So, needUXEval for sure. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #17 from Danat --- (In reply to Heiko Tietze from comment #13) > Don't see how we should deal with issues from one badly designed file. At > least it's not a question for UX. This is a simplified example https://drive.google.com/file/d/1H3sb7j-0PUW5vcJAu-_Xl0VJsFBSfj4N/view?usp=sharing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #16 from Danat --- Created attachment 207177 --> https://bugs.documentfoundation.org/attachment.cgi?id=207177&action=edit Video 2 (sample file simplified) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #15 from Danat --- Created attachment 207176 --> https://bugs.documentfoundation.org/attachment.cgi?id=207176&action=edit Sample file simplified -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #14 from Danat --- (In reply to Heiko Tietze from comment #13) > Don't see how we should deal with issues from one badly designed file. At > least it's not a question for UX. What is "goodly" designed file? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | --- Comment #13 from Heiko Tietze --- Don't see how we should deal with issues from one badly designed file. At least it's not a question for UX. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #12 from Danat --- (In reply to Eyal Rozenberg from comment #11) > (In reply to Danat from comment #10) > > Well, the most important thing is, that whatever the app does - it not be a > surprise for the user. And this does surprise the user, since they're used > to this action affecting the entire column - due to not having selected > anything. > > Tying to the selection is basically the default rule, the question is what > should LO do when it's "difficult" to respect that rule: > > * Should it make a guess what to do for the rows with different column > layout? > * Should it ask the user? > * Should it act on all rows without the split? > * Should it always act on columns based on the column index, on all rows? > * Should it just refuse and say "Non-uniform column layout, please make a > selection" or something along those lines? > > and maybe there are other options still. Tie to selection without removing anything. So people will be able to change width of entire columns without selection the way the do now, but selection will allow to choose which rows to affect and which not to -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #11 from Eyal Rozenberg --- (In reply to Danat from comment #10) Well, the most important thing is, that whatever the app does - it not be a surprise for the user. And this does surprise the user, since they're used to this action affecting the entire column - due to not having selected anything. Tying to the selection is basically the default rule, the question is what should LO do when it's "difficult" to respect that rule: * Should it make a guess what to do for the rows with different column layout? * Should it ask the user? * Should it act on all rows without the split? * Should it always act on columns based on the column index, on all rows? * Should it just refuse and say "Non-uniform column layout, please make a selection" or something along those lines? and maybe there are other options still. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #10 from Danat --- I can see use cases both for single cell width change and for entire column. Consider tying the affected rows to cell selection - so the selected cells will be affected and the others won't. This is intuitive -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||4633 --- Comment #9 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #8) Why would this be a dupe of 114633? This bug is not about the difficulty of using the dialog, it's about the scope of effect of an action, once already taken. It is also not likely to be affected by a revamp of the dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #8 from Heiko Tietze --- *** This bug has been marked as a duplicate of bug 114633 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #7 from Buovjaga --- See also bug 114633 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #6 from Eyal Rozenberg --- Created attachment 206884 --> https://bugs.documentfoundation.org/attachment.cgi?id=206884&action=edit Simplifed reproducer This file requires only the following steps to reproduce (ignoring a sanity check): 1. In the table, right-click the cell on the central column, on the second row 2. On the context menu, choose Table Properties 3. On the Columns tab of the dialog, decrease the middle column width, say by about half (so you would notice the difference). 4. Accept and exit the dialog Expected behavior: After step (4.), the entire column's width has decreased - with the split cells now adding up to the new decrease width. A less-expected, but stil arguably legitimate, effect is for the column widths to change in all rows except for the one with the split cell. Actual behavior: After step (4.), only the second row, in which we had right-clicked, has its column widths change. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #5 from Eyal Rozenberg --- Ok, much simpler reproduction instructions: 1. Create a new Writer document 2. Insert a 4-row, 3-column table (Sanity check phase:) 3. Right-click the cell on the central column of the second row 4. On the context menu, choose Table Properties 5. On the Columns tab of the dialog, decrease the middle column width, say by about half (so you would notice the difference). 6. Accept and exit the dialog 7. On the menu, choose Edit | Undo (Sanity check ends) 8. Right-click the cell on the central cell on the third row 9. On the context menu, choose "Split Cells..." 10. Choose to split "Vertically" into two cells 11. Repeat steps (4.) through (6.) Expected behavior: After step (6.), the entire column's width has decreased. After step (11.), the entire column's width has decreased - with the split cells now adding up to the new decrease width. A less-expected, but stil arguably legitimate, effect is for the column widths to change in all rows except for the one with the split cell. Actual behavior: After step (6.), the entire column's width has decreased - so the sanity check passes. After step (11.), only the second row, in which we had right-clicked, has its column widths change. Now, I suppose one could argue, that once the column distribution is no longer uniform in the table, each column widths change only affects a single row; but - it's difficult to claim that is the user's intent, when they didn't just arbitrarily mess with column widths different on each row, but rather perfored a split, so that the uniform column edge still exists over all rows. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval --- Comment #4 from Eyal Rozenberg --- Ok, much simpler reproduction instructions: 1. Create a new Writer document 2. Insert a 4-row, 3-column table (Sanity check phase:) 3. Right-click the middle cell 4. On the context menu, choose Table Properties 5. On the Columns tab of the dialog, decrease the middle column width, say by about half (so you would notice the difference). 6. Accept and exit the dialog 7. On the menu, choose Edit | Undo (Sanity check ends) 8. Right-click the center cell on the bottom row 9. On the context menu, choose "Split Cells..." 10. Choose to split "Vertically" into two cells 11. Repeat steps (4.) through (6.) Expected behavior: After step (6.), the entire column's width has decreased. After step (11.), the entire column's width has decreased - with the split cells now adding up to the new decrease width. A less-expected, but stil arguably legitimate, effect is for the column widths to change in all rows except for the one with the split cell. Actual behavior: After step (6.), the entire column's width has decreased - so the sanity check passes. After step (11.), only the second row, in which we had right-clicked has its column widths change. Now, I suppose one could argue, that once the column distribution is no longer uniform in the table, each column widths change only affects a single row; but - it's difficult to claim that is the user's intent, when they didn't just arbitrarily mess with column widths different on each row, but rather perfored a split, so that the uniform column edge still exists over all rows. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 Eyal Rozenberg changed: What|Removed |Added Blocks||10 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=10 [Bug 10] [META] DOCX (OOXML) table-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #3 from Eyal Rozenberg --- That is rather weird behavior. Can you try to whittle down the example document to something more minimal? And then, can you perhaps suggest reproduction instructions starting with an empty MS-Word document, and the actions necessary to create the DOCX which triggers this behavior in LO Writer? I'm asking because when I create tables in LO Writer, they don't behave this way. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #2 from Danat --- Created attachment 206878 --> https://bugs.documentfoundation.org/attachment.cgi?id=206878&action=edit File in the video -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171913] Column size in Table properties affects only one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=171913 --- Comment #1 from Danat --- Created attachment 206877 --> https://bugs.documentfoundation.org/attachment.cgi?id=206877&action=edit Video -- You are receiving this mail because: You are the assignee for the bug.
