<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Inserting an image into header causes pages to be added in an infinite loop" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122862#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Inserting an image into header causes pages to be added in an infinite loop" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122862">bug 122862</a> from <a class="email" href="mailto:tim@retout.co.uk" title="Tim Retout <tim@retout.co.uk>"> Tim Retout</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=122862#c7">comment #7</a>) > If the question for UX is what to do with badly sized images we could > a) accept the input (and make sure the page count is not affected), > b) scale to fit into the actual header (which makes it consequently > impossible to exceed the page size on resizing), or > c) crop the image. > I would prefer a) over b) and refuse c). Given the second test case, where a much smaller image can trigger the same behaviour, I think it will be difficult to determine whether an image is "badly sized". My hunch is that the bug lies in the fact that text reflowing is triggered at all, perhaps... I guess I find it unexpected that a header image can sit outside of the header area and cause text in the body to wrap around it. UX-wise, I'd expect consistency between headers and footers, but I haven't confirmed for myself how the footer behaviour differs.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>