Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-device-adapt] consider adding user-overscroll-action descriptor #455

Closed
majido opened this issue Sep 8, 2016 · 6 comments
Closed
Assignees

Comments

@majido
Copy link
Contributor

majido commented Sep 8, 2016

We are collaborating on a new declarative API to give developer a reliable way to control overscroll actions (e.g., swipe navigations, pull-to-refresh, etc.).

Our initial thinking was to use a new CSS attribute but it was pointed out that perhaps a descriptor in the viewport meta tag is a better API particularly because all of the overscroll actions that we care about are only meaningful for viewport.

The proposal is to add user-overscroll-action which will be similar to user-scalable property in the viewport meta in the sense that it provides a directive to user agent on how to interpret a user action in this case overscroll as opposed to zoom.

Do you think such a proposed descriptor is appropriate for css-device-adapt?

/cc @smaug----

@majido
Copy link
Contributor Author

majido commented Dec 1, 2016

Friendly ping 😃 (I assume relevant editors triage these issues once get labeled)

As explained we are looking to find the most appropriate API for exposing such controls. Here are the options we have considered so far:

  1. A generic CSS attribute (this was the original proposal and it is what we are currently implementing in Blink behind a flag)
  2. A new property on viewport meta as part of css-device-adapt (this issue)
  3. As an extension to existing "-ms-scroll-chaining" and spec'ed as part of CSSOM View (this was proposed quite recently)

At this point I prefer options 2 or 3 if possible. I appreciate your feedback on this issue which would help guiding us in deciding which of these options to pursue further.

@frivoal frivoal self-assigned this May 16, 2017
@xfq
Copy link
Member

xfq commented Jan 17, 2018

IIUC, this is now called overscroll-behavior?

@jonjohnjohnson
Copy link

Guessing this can be closed in light of #2179 resolution ?

@frivoal
Copy link
Collaborator

frivoal commented Jun 22, 2018

I think so. @majido , is that OK with you?

@majido
Copy link
Contributor Author

majido commented Jul 2, 2018 via email

@xfq
Copy link
Member

xfq commented Jul 2, 2018

Closing.

@xfq xfq closed this as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants