window scroll bindings are bidirectional #461
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #404. With this PR, in a situation like this...
...changing the value of
y
programmatically will result in the window scrolling. (The value ofy
remains constrained to the scrollable range.)In a lot of situations this kind of bidirectional binding is unnecessary, but it would violate expectations if it didn't work this way so I think it's worth the modest overhead, which basically amounts to this:
Combined with an
animate
ortween
method (#236), this would provide a very straightforward way of smoothly scrolling to a section of the page, for example.