Top controls are an ill-specified part of the platform and cause headaches for developers and users alike. I think Chrome in particular is bad here. I've summarized the issues, various browser differences, and potential changes in a design doc: https://docs.google.com/document/d/1kyOHTOJ_qcapdaxChds_hSBG3nSpawllEQoHvtMEcvA/edit?usp=sharing
Let me know what you think
To unsubscribe from this group and stop receiving emails from it, send an email to input-dev+...@chromium.org.
As a web developer, following Safari will be a real downgrade. This simply encourages developers to use JavaScript instead of CSS and that is never what you want.
Also as a web developer, the top-controls-disappear-while-scrolling feature is also a pretty awful feature. For some reason, almost every browser adopted it (I understand the purpose, which is fair - more real estate on mobile), even though it is simply developer (and sometimes user) hostile.Hiding the top controls creates some sort of a full screen situation which can be deceiving for the user, if it is used in the wrong manner.
What about the proposal do you see as a problem? The basic premise is that we wont be resizing the initial containing block every time the top controls show/hide. This allows developers to use more CSS, not less (vh units become practical, for instance).