Ticket #2613 (new defect)

Opened 7 years ago

Last modified 6 years ago

Unwanted mouse events when laptop is closed: Need better bumpers

Reported by: shenki Owned by: mlj
Priority: normal Milestone: Gen2
Component: hardware Version:
Keywords: ebook Cc:
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

When using XO in ebook mode, holding with portrait orientation, a comfortable position for the hand is the top of the screen.

This causes the back of the screen to push down on the mouse button, as well as move the cursor, causing unexpected movement around the document you are trying to read.

With the screen completely covering the touchpad, is there any reason to still accept mouse input? With the new touchpad, we will be able to power it down, but it is still an issue for <=B4 units.

Change History

Changed 7 years ago by jg

Could you demo this for me Wednesday?

Changed 7 years ago by jg

  • owner changed from jg to Eben
  • component changed from distro to design
  • milestone changed from Untriaged to Gen2

Mary Lou: the bumpers at the corners of the keyboard assembly are not providing enough clearance. I can easily press a button by accident.

Joel, we can (should) clearly turn off the keyboard/touchpad when in either ebook mode or closed, if only to save power; now you've made an even stronger argument...

See #2770 and #1407.

I put this one's milestone to Gen2, having opened #2770, to remind us about the mechanical design issue.

Changed 7 years ago by Eben

  • owner changed from Eben to mlj
  • component changed from design to hardware
  • summary changed from Unwanted mouse events in ebook mode to Unwanted mouse events when laptop is closed: Need better bumpers

I attached the same comment to #2770: The mouse cursor should also be hidden when this happens, so that a) it doesn't get in the way in ebook mode from which it can't me moved out of the way and b) it doesn't confuse users into thinking there is a way to move it.

This has been in the spec for some time now, and is clearly needed. Since this should happen regardless of whether or not these lower level changes are made to turn off input, I'm going to file a separate ticket (#2954) for it. It will at least prevent the trackpad from being a nuisance, though it can't prevent the mouse button from being a problem.

Since all the issues other than the hardware design itself now have their own in their corresponding tickets, I'm setting this back to hardware.

Changed 6 years ago by bemasc

IMHO: Once #2770 is fixed, this does not need to be fixed. It will be a non-bug. The hardware team should not incur any expense or stress attempting to fix this.

Note: See TracTickets for help on using tickets.