soc-pe-bot
commented
9 months ago Team's Response
Since this is not a diagram being split into two, we feel that it does not hinder the reader:
As such, we propose to reject this bug report.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for your response. However, I feel that this should still count as a documentation bug with a Very Low severity.
According to this screenshot of the paragraph, I feel that there is "too much white padding" which can potentially hinder the reader. It also makes sense that the header of a section should be on a fresh page. In my opinion, the team could have easily circumvented this issue by placing a <div style="page-break-after: always;"></div> tag inside the markdown of the Developer Guide, according to the PDF printing instructions, to shift the heading to the next page after printing the PDF version.
It would be hard for the user to refer to the Commands for Applicant Processing Features as whole. Imagine if the user wants to print out this section as a hardcopy reference but the title and content are split over two pages, it would bring some level of inconvenience to the user.
The "Commands for Applicant Processing Features" heading is split from the rest of the table on page 22 of the User Guide which can affect readability.