Closed jgraham closed 4 months ago
cc @nechaev-chromium
After merging this I noticed we have some uniformly passing tests that assume that input like {x: 200}
is just silently ignored rather than either producing an error or setting the x-coordinate to 200 (where possible). Silently ignoring broken input seems like bad design, but I guess I should revert that part on the basis that's the defacto behviour.
Previously it was unclear if it was acceptable to return without error from set window rect if the implementation is unable to set some of the properties.
This updates the spec so that:
It's unambiguously OK to run the command even if you don't support some aspects of the functionality on the current platform / configuration (you are expected to continue to return an error if you don't support any aspect of the functionality).
It's clear that both position and dimension properties are best effort, and even if you are able to adjust them there's no guarantee that you get the exact requested values.
It's clear what to do if you get just an x coordinate but not y, or just width but not height, or vice-versa. Previously this was undefined.
Preview | Diff