Created attachment 118245 [details]
Here a doc that provide a visual example of the bug.
In table in writer
1. Select a table cell (full cell selection, not just the text) in the second column or second row.
2. apply a style (like Header 1 or bullet).
The style in the selected cell changed ... and the styles of a neighbor cell also changed (not wanted).
Only the style in the selected cell changed.
Reproducible with LO 220.127.116.11, Win 8.1
If I insert a 4x4 table in a new WRITER document and select the whole cell in row 2 / column 2 and change it to numbering style with the icon in the toolbar at the top then the cell in row 2 / column 1 gets also the numbering style.
To reproduce it you need to select the whole cell not only the text (as mentioned in the bug description) and you need to mark the cell from its right border to the left border (going with the mouse from the right border of the cell to the cell to the left while holding the left mouse button, then going back that not both cells are selected). If you do it the other direction it is not reproducible.
Can not reproduce with Version 18.104.22.168 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89, win7 -> regression
I can reproduce with Version: 22.214.171.124.alpha0+
Build ID: 57d6b92b69a31260dea0d84fcd1fc5866ada7adb, win7
Reproducible with Version: 126.96.36.199.alpha1+
Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3
bibisect-43max$ git checkout oldest
Migrating Whiteboard tags to Keywords: (bibisectRequest)
Either I'm not understanding this bug correctly or I'm not able to reproduce.
Build ID: 5df326438fd3a5613a52b4de1935426911ff1301
I can reproduce with the following steps:
1. Make 4x4 table in new Writer document
2. Row1 Column1 write "a"
3. Row2 Column1 write "b"
4. Press and hold left mouse button on cell with the "b"
5. Drag mouse cursor up to cell with the "a": both cells are highlighted
6. Drag mouse cursor back to cell with the "b": only cell "b" is highlighted
7. Let go left mouse button
8. On the right-hand side choose "Heading 1" in the Styles menu
9. Both cells' contents are formatted
Regarding comment 6:
Was reproduced on:
Windows 10 Pro, Version 1511 (OS Build 10586.36)
Version: 188.8.131.52 Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
Locale: de-DE (de_DE)
Bodhi Moksha (fork of Ubuntu 14.04)
LibreOffice 3.3 - 5.2 dev
Following the instructions in comment 6 as well as a video that Raal sent me - I see the same behavior going all the way back to 3.3 (inherited from OOo). I'm updating the status.
@Raal - if you don't mind checking again to see if you can find a regression here....I followed your steps (and FutureProject's steps) exactly and I see the same behavior throughout (from 3.3 - 5.2).
Dangit sorry for the noise - I lied, I can see the regression....updating now (sorry again!)
Bibisect 35all package (3.5 - 4.2)
I can confirm the problem throughout the bibisect package but 3.3 doesn't show the problem so it is a regression.
Adding 'preBibisect' keyword...
[This is an automatic message]
Changing version to 184.108.40.206 in order to get rid of 'preBibisect' version as 220.127.116.11 looks to be the last version not covered by bibisect-43all.
Still repro with:
Build ID: a296a69c984b17cfbcd249cf6bdc191d08dff2a6
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-02-06_00:00:55
On pc Debian x86-64 with master sources updated 2 days ago or with LO Debian package 18.104.22.168, I don't reproduce this.
I retrieved the attached file and applied style "Heading 1" of the right bottom cell of first array, only the cell was changed.
Did I miss something?
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!