> so I'm a bit confused about how would any of this help?
Yes I have div and border and other PoCs that reveal entropy, right there on TZP :) Solving subpixels isn't a zero-sum game. If we can make scripts have to touch the dom or implement more perf costly measures, then we're in.
IANAE on the moz code base - I don't want to touch everything (or lots of things), just those specific items above - for example we're not actually changing the actual inner size (`width`), we're just returning `width` (when we ask for `min-width`). As for screen, surely forcing an integer there will not beak web content.
Maybe this is too hard to engineer - I was just hoping there was an easy "input" part where the code could swap e.g. `width` for `min-width`
Bug 1672093 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> so I'm a bit confused about how would any of this help?
Yes I have div and border and other PoCs that reveal entropy, right there on TZP :) Solving subpixels isn't a zero-sum game. If we can make scripts have to touch the dom or implement more perf costly measures, then we're in.
IANAE on the moz code base - I don't want to touch everything (or lots of things), just those specific items above - for example we're not actually changing the actual inner size (`width`), we're just returning `max-width` (when we ask for `width`). As for screen, surely forcing an integer there will not beak web content.
Maybe this is too hard to engineer - I was just hoping there was an easy "input" part where the code could swap e.g. ~~`width` for `min-width`~~ `min-device-width` with `device-width`
edit: fixup parameters
> so I'm a bit confused about how would any of this help?
Yes I have div and border and other PoCs that reveal entropy, right there on TZP :) Solving subpixels isn't a zero-sum game. If we can make scripts have to touch the dom or implement more perf costly measures, then we're in.
IANAE on the moz code base - I don't want to touch everything (or lots of things), just those specific items above - for example we're not actually changing the actual inner size (`width`), we're just returning `max-width` (when we ask for `width`). As for screen, surely forcing an integer there will not beak web content.
Maybe this is too hard to engineer - I was just hoping there was an easy "input" part where the code could swap e.g. ~~`width` for `min-width`~~ `min-device-width` with `device-width` (edit: and only in css and matchMedia)
edit: fixup parameters