Users are complaining that when using Chromebooks in docked mode (i.e. external display connected and lid closed) with Type-C docks used to connect the display and external input devices, they're unable to use those input devices to wake the device from S3 after it idle-suspends.

  eve: http://g/chromeos-discuss/Ds5lrZX1k-o
samus: http://g/chromeos-discuss/bdO-otq_sGw

Instead, they need to open the Chomebook's lid to wake it, which is annoying and also results in their windows getting reconfigured due to the existence of the additional internal display.

What's the expected behavior here with regard to:

a) powering Type-C ports while in S3, and
b) waking in response to input events from devices connected via Type-C docks?

I suspect that this is unrelated to docked mode; it's just more annoying when in that state because you need to open the lid to get to the internal keyboard to wake the device.

Input devices connected via Type-A ports haven't had problems like this, to the best of my knowledge.
 

Users are complaining that when using Pixelbooks in docked mode (i.e. external display connected and lid closed) with Type-C docks used to connect the display and external input devices, they're unable to use those input devices to wake the device from S3 after it idle-suspends.

See e.g. http://g/chromeos-discuss/Ds5lrZX1k-o

Instead, they need to open the Chomebook's lid to wake it, which is annoying and also results in their windows getting reconfigured due to the existence of the additional internal display.

What's the expected behavior here with regard to:

a) powering Type-C ports while in S3, and
b) waking in response to input events from devices connected via Type-C docks?

I suspect that this is unrelated to docked mode; it's just more annoying when in that state because you need to open the lid to get to the internal keyboard to wake the device.

Input devices connected via Type-A ports haven't had problems like this, to the best of my knowledge.