Link to issue number:

Follow-up of #15057

Summary of the issue:

In the GUI, the recent trend is to disable (grey out) the options that are not applicable due to the values of other options.
New option "Ignore blank lines for line indentation reporting" has no sense when report indentation is OFF. Thus it should be greyed out when report indent is off.

This is especially needed to reduce the number of tab presses when navigating in the Doc formatting settings dialog which contains a lot of items.

Description of user facing changes

Option "Ignore blank lines for lineis greyed out when report indent is off and enabled when other indent reporting types are configured.

While at it, in this PR, I have also changed the context help target for "Ignore blank lines" option. Before it was jumping by default to "Document formatting settings" paragraph; now it jumps to "Line indentation reporting" paragraph, which contains more precise information on this topic.

Description of development approach

See code.

Testing strategy:

Manual tests:

1. For each value of indent reporting:

• Check that "Ignore blank lines..." is greyed out or not when opening doc formatting settings
• Check that "Ignore blank lines..." is greyed out or not when changing the indent report mode in the combobox

2. Check with appVeyor build the context help target.

Known issues with pull request:

• In doc formatting settings, one may think that similar handling should be applied to table related options. But it should not instead. Because when using table nav commands, we can have coordinates reported even if tables are not reported (as a container)
• I have not checked all the settings (and that's not suitable for a PR against beta); but there are other options in settings that may be greyed out depending on the value of another option. If there is a need for it, a new PR will be submitted.

Change log

Not needed: small change + applies to unreleased feature.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.