This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section "10.1 Determining if an element is displayed" mentions that "The User Agent MUST NOT allow negative scrolling." Is trying to define what a User Agent MUST do out of scope of this spec? Should we just delete that sentence or formulate it as a prescription for the WD remote end?
The spec is designed to tell the User Agent (the browser) what it MUST/SHOULD do or not do. In this case browsers never do negative scrolling but if they ever do we have it in writing that it should never be handled.
So that means that it should tell "The remote end MUST NOT allow negative scrolling."
David, I believe the distinction between (similarly sounding) "what browser should/must do" and "what WD remote end should/must make the browser do" is important. We know that the spec is for 'implementors of the WebDriver API', that it describes two components - local and remote ends - and that implementors are not necessarily people who have complete control over browser behavior in certain situations. In the ideal situation, implementors of WebDriver are a browser vendor and they have some control, but even then WebDriver API doesn't feel right place to define what browser should/must do in WebDriver-irrelevant situations (such as supporting or not supporting negative scrolling); for that there are other specs. Does this make sense? We could defer it to the F2F or something since it doesn't appear to be blocking anything. Now I also noticed several other places in the spec with 'user agent must/should'.
I agree with the premise of this bug, but I think all the instances are fixed now. If not please open specific bugs.