I merge the cells in the table in LO Writer and try to orient the text from bottom to top. When I leave the table and click on the merged cells again and try to type or change the text LO Writer displays "Write - protected content cannot be changed". Is this happening to someone else or just me and how to fix it? I'm using LO 6.3.5 on Linux Mint OS 19.3.
I ca't confirm it with
Version: 22.214.171.124 (x64)
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win;
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present.
The profile is reset and it's all the same again. This only happens when the vertical cells merge (per column).
I think I can reproduce this. Detailed steps to reproduce:
1. Create a new blank document with Writer;
2. Table > Insert Table..., insert a 5-row by 5-column table;
3. Use mouse to drag and select the four vertical cells on the left-bottom corner, i.e., the first cells of row 2, 3, 4 and 5;
4. Table > Merge Cells;
5. Table > Properties... > Text Flow, change text direction to "vertical (bottom to top)";
6. Type two lines of random text, end each line with Enter key (for some reason the text is invisible on my system, but that's probably for another bug);
7. Click in anther cell and click back into the merged cell;
8. Press Backspace key;
9. Write protection dialog pops up.
Reproduced with both 6.3.5 and 6.4.1 RC1 on Windows 10:
Version: 126.96.36.199 (x64)
Build ID: dd0751754f11728f69b42ee2af66670068624673
CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win;
Locale: zh-CN (zh_CN); UI-Language: en-US
版本: 188.8.131.52 (x64)
Build ID: 56f3c78975db08733f771c53643b5d1aa7c57567
CPU 线程: 2; 操作系统: Windows 10.0 Build 18363; UI 渲染: 默认; VCL: win;
区域语言: zh-CN (zh_CN); UI 语言: zh-CN
I'll refrain from confirming this bug until someone else (looking at Dieter :-) can reproduce with my steps.
Ming, if you can confirm a bug, you are also allowed to change status to NEW
But now I can also confirm it with
Version: 184.108.40.206.alpha0+ (x64)
Build ID: 41177730421f9be9ad955766a5a19667d8003b11
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win;
Locale: de-DE (de_DE); UI-Language: en-GB
(In reply to Dieter from comment #4)
> Ming, if you can confirm a bug, you are also allowed to change status to NEW
Thanks Dieter, I know and I've done that for other bugs.
It's just that for this one, the reporter's description is so vague that I'm not sure I'm reproducing exactly what he experienced. So I'd rather wait for a second (third?) opinion.
Ming Hua,your description is what is actually happening.
My English is weak and this is why it's a weaker description.