https://bugs.documentfoundation.org/show_bug.cgi?id=150728

            Bug ID: 150728
           Summary: Formatting Aids settings for LibreOffice Writer/Web
                    are ignored
           Product: LibreOffice
           Version: 6.3.6.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: stephane.guil...@member.fsf.org

Description:
The Formatting Aids settings specific to the Web view are ignored, and the
general Formatting Aids settings are used instead.

Steps to Reproduce:
1. Open Writer
2. "View > Web"
3. Make sure that "View > Formatting Marks" is on
4. Write a couple of words, press enter
5. Got to "Tools > Options > LibreOffice Writer/Web > Formatting Aids" and
change some settings (like unticking the markers for Paragraph ends and for
spaces)
6. Click OK

Actual Results:
This has no impact on the formatting marks displayed on the page. In fact, it
is the settings in "Tools > Options > LibreOffice Writer > Formatting Aids"
that are used.

Expected Results:
The formatting aids settings specific to the Web view are taken into account in
the Web view.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I feel like LibreOffice would benefit from removing this web-specific
Formatting Aids section entirely, and follow a single set of formatting aids
settings for both the Normal and Web views.

Tested in:

Version: 6.3.6.2
Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; 
Locale: en-AU (en_AU.UTF-8); UI-Language: en-US
Calc: threaded

and:

Version: 7.5.0.0.alpha0+ / LibreOffice Community
Build ID: 24087697d5cf78aac346d4dcea0596373e15a95c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to