- From: bokand <notifications@github.com>
- Date: Mon, 24 Jul 2017 14:27:24 +0000 (UTC)
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 24 July 2017 14:28:14 UTC
If the property doesn't react to ctrl+/- zooming then it isn't in CSS pixels since that increases/decreases the size of a CSS pixel. Other properties like window.innerWidth do change as the user zooms in and out. DSF = device scale factor. It's the zoom applied by the browser to compensate for a high pixel density display (i.e. so that the UI doesn't look tiny). That's what we call it on Chrome, not sure what other browsers call it. We should be careful about compat impact but in this case, since we're already applying the DSF to these properties, content that will break wit this change would already have been broken on high density displays so I suspect regressions would be rare. Users could work-around by resetting zoom level so any issues would be low severity IMO. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/150#issuecomment-317439940
Received on Monday, 24 July 2017 14:28:14 UTC