Hi Isomorphic,
your BrowserZoom did not change between 12.0p and 12.1d, yet.
I clicked some of the bugs you linked and a quite few are fixed now. I do know that the limitations still apply, as a customer of ours has a problem here with non-stop scrollbar-related resizes and therefore a flickering display and is complaining about it (we do not have tried detect-zoom.js, yet).
Then I found also this in the linked SO post from your docs
Best regards
Blama
your BrowserZoom did not change between 12.0p and 12.1d, yet.
I clicked some of the bugs you linked and a quite few are fixed now. I do know that the limitations still apply, as a customer of ours has a problem here with non-stop scrollbar-related resizes and therefore a flickering display and is complaining about it (we do not have tried detect-zoom.js, yet).
Then I found also this in the linked SO post from your docs
- Chrome visualViewport API: https://www.chromestatus.com/feature/5737866978131968
- W3C draft from March 2019: https://wicg.github.io/visual-viewport/
- Are there changes in support to expect in 12.1p for browser zoom (I assume no)?
- Can update those docs w.r.t. to the browser issues?
- Does the visualViewport API from above help you to integrate a function like the detect-zoom.js directly into the framework and can you do this this way or another?
As the Zoom issue affects all developer-users of the framework and their end-users, an enabled-by-default way of warning that this is unsupported would be great.
With the way it is currently, one has to get bug reports from the users and then look up your docs, finally finding out that is not supported and then perhaps try to build oneself a no longer maintained project to perhaps detect zoom changes. It would really help everyone if this instead would be built-in and active by default.
Best regards
Blama
Comment