You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the existing pattern of the browser frame, I would not expect the overlay to change size when zooming the page. The overlay would match the size of the title bar on any other installed PWA
Good catch @BoCupp-Microsoft. As @amandabaker said, the overlay would not resize, but the web content acting as a title bar would. So you could end up with the title bar getting much larger (or even smaller) than the controls. As pixels are no longer fixed in dimension (i.e., they scale like other relative values) I'm not quite sure how you'd be able to force the title bar to remain at a consistent size (at least not without using JS to listen for a synthetic text resize event and then applying some logic to scale it up/down relative to the root font size and your target height). We should dig into this a bit more.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from MicrosoftEdge/MSEdgeExplainers#309
@BoCupp-Microsoft opened this issue on 2020-05-07
If I zoom the page should the title bar content get bigger? Maybe there is already a CSS mechanism to handle this?
@amandabaker commented on 2020-05-07
@aarongustafson commented on 2020-05-08
Good catch @BoCupp-Microsoft. As @amandabaker said, the overlay would not resize, but the web content acting as a title bar would. So you could end up with the title bar getting much larger (or even smaller) than the controls. As pixels are no longer fixed in dimension (i.e., they scale like other relative values) I'm not quite sure how you'd be able to force the title bar to remain at a consistent size (at least not without using JS to listen for a synthetic text resize event and then applying some logic to scale it up/down relative to the root font size and your target height). We should dig into this a bit more.
The text was updated successfully, but these errors were encountered: