1) Open Writer
2) Insert a shape or textbox
3) Notice that Style > Edit Style is still enabled
4) Clicking it will open paragraph style dialog
.uno:EditStyle shouldnt be enabled like Update Style (.uno:StyleUpdateByExample) and New Style (.uno:StyleNewByExample) arent.
Build ID: 44b14e8c7c485d8a3bb99d9484ac63273988b633
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-04-17_03:32:22
Locale: en-US (en_US.UTF-8); Calc: group
Build ID: 7635e0c1c7f821a1081f8e3868f641ae74a172d6
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); Calc: group
(In reply to Yousuf Philips (jay) from comment #0)
> 1) Open Writer
> 2) Insert a shape or textbox
> 3) Notice that Style > Edit Style is still enabled
> 4) Clicking it will open paragraph style dialog
So expected would be that a dialog appears to edit the Graphic/Frame style.
(In reply to Cor Nouws from comment #2)
> So expected would be that a dialog appears to edit the Graphic/Frame style.
No the command should be disabled, as there is are styles for shapes/textboxes in Writer. Select a textbox and see what happens in Styles & Formatting. Graphic/Frame style is for images and frames.
(In reply to Yousuf Philips (jay) from comment #3)
> No the command should be disabled, as there is are styles for
> shapes/textboxes in Writer. Select a textbox and see what happens in Styles
> & Formatting. Graphic/Frame style is for images and frames.
But why should "Style > Edit Style .." be not context sensitive?
(In reply to Cor Nouws from comment #4)
> But why should "Style > Edit Style .." be not context sensitive?
I'm saying that it should be context sensitive, which presently it isnt. :D
(In reply to Yousuf Philips (jay) from comment #5)
> I'm saying that it should be context sensitive, which presently it isnt. :D
ah :) Sorry that I misread this!
** 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!
Still reproducible with
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: de-AT (de_AT.UTF-8); UI-Language: en-US
Also in the Notebookars.