Bug 133099 - UI: Disable non-usable attributes for form controls in view mode
Summary: UI: Disable non-usable attributes for form controls in view mode
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Form-Controls
  Show dependency treegraph
 
Reported: 2020-05-16 19:35 UTC by Telesto
Modified: 2024-06-05 19:25 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (9.19 KB, application/vnd.oasis.opendocument.text)
2020-05-16 19:37 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-05-16 19:35:07 UTC
Description:
UI: Multiple (4) formatting options for Multi -line with formatting textbox

Steps to Reproduce:
1. Open the attache file
2. Enter the form text box
3. Notice three options to change the font (sidebar/ top menubar and special formatting bar) and the right click menu 

Based on/source (bug 107092)

Actual Results:
4 options to format

Expected Results:
Remove the context depended toolbar


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha1+ (x64)
Build ID: f9790da286f2d2fa47f1748f8cfa6172c6622ca3
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: de-CH (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-05-16 19:37:17 UTC
Created attachment 160911 [details]
Example file
Comment 2 Heiko Tietze 2020-05-18 10:54:11 UTC
We always provide different ways to access a function. Some people don't lile the sidebar (eg with small screens) some work without toolbars etc. In this situation you cannot use any but the context menu since the form control is not in design mode. That's not a bug.
Comment 3 Telesto 2020-05-20 17:56:27 UTC
(In reply to Heiko Tietze from comment #2)
> We always provide different ways to access a function. Some people don't
> lile the sidebar (eg with small screens) some work without toolbars etc. In
> this situation you cannot use any but the context menu since the form
> control is not in design mode. That's not a bug.

We always provide different ways to access a function.. 
Yes, didn't question that... Bu four way's maybe a little overblown..

* A context depended textbox formatting toolbar
* Sidebar
* Regular formatting toolbar
* Right click context menu

Not seeing the net worth for context depended formatting toolbar.. 

In this situation you cannot use any but the context menu since the form control is not in design mode.

-> Not sure what you're saying here

In design mode.. 
* Default toolbar disabled
* No right click menu
* No formatting in the sidebar
* No context dependend textbox formatting toolbar

With design mode disabled
* A context depended textbox formatting toolbar
* Sidebar formatting toolbar (enabled)
* Regular formatting toolbar (enabled)
* Right click context menu

The only way to set the font/font size for textbox is Right Click formatting menu. Even the context depended toolbar does not work [but that's not exactly the scope of this bug..)
Comment 4 Heiko Tietze 2020-05-22 13:19:19 UTC
If you turn the issue into "Disable non-usable attributes for form controls in view mode" I agree. But still -1 to remove one a formatting workflow (and if, which to retire?).
Comment 5 Telesto 2020-05-22 13:35:42 UTC
(In reply to Heiko Tietze from comment #4)
> If you turn the issue into "Disable non-usable attributes for form controls
> in view mode" I agree. But still -1 to remove one a formatting workflow (and
> if, which to retire?).

The whole point was about form controls + formatting (in view mode). But i'm not really good at the specific 'UX-language'. So please rephrase my problem..
Comment 6 Heiko Tietze 2020-05-22 14:50:26 UTC
Sounds like a reasonable request now.
Comment 7 QA Administrators 2022-05-23 03:37:15 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-05-23 03:17:16 UTC
Dear Telesto,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug