-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixups, improvements, further work - previously: added css rules to return blanks outside our range - previously: fixed generic query for getting property to return `x` if outside range - the range limitations means we don't always get a bypass (when someone is lying): factors include - the real measurements - zoom (as you zoom in, the values returned are smaller and vice versa) - system scaling (not tested but this would be similar to zoom) - seems as if desktop's minimum width is now 450px (at normal system scaling/zoom) - will consider expanding the lower bounds to 400 or 350, but I think we need a new approach that if we haven't done a bypass, then we should use JS and css injection to bisect the real value - only needed if (I think), prototype lies shows that BS is going on - allows 1px less in the pseudo value as a match (due to using `min`), and upgrades it to match (which helps with computations) - the recalculated screen value at 100% uses common corrections - it already rounds to the nearest even number, but sometimes (when it uses the bypassed values, even when rounded by by 1px) it's off: this is due to using the device pixel ratio PoC which is not as accurate after six or so decimal places - the gLieBypassed is pushed the recalculated value - section metrics - stable in fullscreen (luckily FS is not all 0,0 coordinates) - removed compare metrics - fixes inconsistencies to make it stable in FS - can't use them anyway: screen might be different from the rest due to recalculated-100%-zoom value, etc - this simplifies the logic: just return screen + coordinates-match for now - added screen prototype lies if we failed to bypass More to do though
- Loading branch information
1 parent
053dea7
commit b36f53b
Showing
1 changed file
with
110 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters