(No comment was entered for this change.)

(No comment was entered for this change.)

Having used the lion interface for a little while the key difference to me is whether you are grabbing the content or the frame.  I suggest naming the two options that way rather than "legacy" and "natural".  Those names are biased and unuseful.

For a touch screen it is clearly (to me) natural to be grabbing the content;  that's what your fingers are on.

For me, I feel like a trackpad is a part of the metal frame, but I can see where others might think of it as an opaque hole through a physical frame.

This would be an essential feature only if we are planning ChromeOS on touch screen devices. So if at all it is implemented; it should be an option to select with default being legacy way to avoid the confusion.

Touch screens appear to be what drove Apple's rethink in Lion (similarity to iOS, according to the press), since they are in some ways opposite to the pre-existing convention.

A natural paradigm/interpretation is a combination of experiences and physical analogies.  Either direction is rational, especially (as the original requester pointed out) to those who use multiple similar devices.

The feature proposed is an opportunity to make an emerging/growing set of users happier with Chrome devices with touchpads. 

(No comment was entered for this change.)

(No comment was entered for this change.)

Having used this a while myself, I like it. I think it could be a good candidate for about:flags, and we can gauge user feedback.

 Issue 18690  has been merged into this issue.

Inheriting labels from duplicate bug.

This doesn't need to go in about:flags.  If we implement support for this, we should be able to control it from the normal chrome prefs page.

It does bear consideration, though...what is the sense of the y-axis on the login screen?  Owner preference?

I'm not aware of any piece of scrolling UI on the sign in screen, but if there is now or will be some scrolling UI then I think owner preference is a good choice given the significant # of devices which will have just one or two users.

 Issue 18456  has been merged into this issue.

For now, given the crowded Settings page, let's get this in about:flags first. +Dave, can you look into this when you get a chance?

 Issue 20304  has been merged into this issue.

Those of us who regularly use both a Mac and Chromebook are definitely looking forward to this option.  Thanks. :)  It almost feels like this could be grouped with the "swap the option" key toggle.  Basically instead a "behave like Windows" vs "behave like Mac" toggle.

Please don't post "I'd like to see this too!" comments on bugs, no matter how genial.  Star issues to vote for them.  It's the only scalable way for us to gauge interest.

Moving non-essential bugs to R17. please move back if this was done in error and your bug is a blocker for R15 or R16.

 Issue 24268  has been merged into this issue.

Issue 24416 has been merged into this issue.

Moving bugs marked as Started but not blockers from R17 to R18.  Please move back if you think this is a blocker, and add the ReleaseBlock-Stable label. 

Assigning to Glen to see if we want to officially support inverted scrolling & thus have UI. 



For those of you who like to play developer mode, are running an R18 or older build on Samsung Series 5 or the Acer AC700, here is quick hack to get this to work (not guaranteed to work everywhere):

Go to shell
$ xinput list
Look for ID number of trackpad, such as 11
$ xinput set-button-map <trackpad_ID> 1 2 3 5 4 7 6

Issue 25549 has been merged into this issue.

Inheriting labels from duplicate bug.

 Issue 25921  has been merged into this issue.

There's a chromium bug for this

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)