(In reply to Botond Ballo [:botond] from comment #17) > So, possible solutions for this one are: > > * Decreasing the full-zoom _does_ decrease the RDM pane's width (i.e. bug 1572840) The patches for Bug 1572840 seem plausible and likely to land. I'll check this bug against a build with those patches applied. > * We allow `MobileViewportManager` to "veto" full-zoom-out events if they would cause the content width to underflow the RDM pane width I think there are other reasons to consider a veto. By doing a full-zoom too far, with patches for Bug 1572840 applied, it's trivial to make the RDM pane exceed the bounds of the browser window. It's such a bad user experience, particularly with the horizontal excess, that we'll probably want to prevent this from happening.
Bug 1561227 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Botond Ballo [:botond] from comment #17) > So, possible solutions for this one are: > > * Decreasing the full-zoom _does_ decrease the RDM pane's width (i.e. bug 1572840) The patches for Bug 1572840 seem plausible and likely to land. I'll check this bug against a build with those patches applied. > * We allow `MobileViewportManager` to "veto" full-zoom-out events if they would cause the content width to underflow the RDM pane width I think there are other reasons to consider a veto. By doing a full-zoom too far, with patches for Bug 1572840 applied, it's trivial to make the RDM pane exceed the bounds of the browser window. It's such a bad user experience, particularly with the horizontal excess, that we'll probably want to prevent this from happening.
(In reply to Botond Ballo [:botond] from comment #17) > So, possible solutions for this one are: > > * Decreasing the full-zoom _does_ decrease the RDM pane's width (i.e. bug 1572840) The patches for Bug 1572840 seem plausible and likely to land. I'll check this bug against a build with those patches applied. > * We allow `MobileViewportManager` to "veto" full-zoom-out events if they would cause the content width to underflow the RDM pane width I think there are additional reasons to consider a veto. By doing a full-zoom too far, with patches for Bug 1572840 applied, it's trivial to make the RDM pane exceed the bounds of the browser window. It's such a bad user experience, particularly with the horizontal excess, that we'll probably want to prevent this from happening.