Open SelwynAng opened 9 months ago
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.
Team chose [response.Rejected
]
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 Command Parameters as a whole if they want to print it out as reference too and I think that this should qualify as a documentation bug as it reduces the professionalism of the guide.
Under the "Interview Management Features", the "Command Parameter" heading is not on the same page as the table itself which affects readability.