Issue metadata
Sign in to add a comment
|
Partial screenshot feature unusable
Reported by
jim.dantin@chromium.org,
Apr 23 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.69.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Platform: 10452.69.0 (Official Build) beta-channel auron_yuna Steps to reproduce the problem: 1. Use keyboard shortcut to initiate partial screenshot 2. Note that selector icon appears 3. Unable to select region - cannot highlight region of display What is the expected behavior? While holding down touchpad, highlight and select region of screen What went wrong? Nothing highlighted, full screenshot is captured. Did this work before? Yes Previous beta version Chrome version: 66.0.3359.117 Channel: beta OS Version: 10452.69.0 Flash Version: Also reported by a user on Chromebook Central https://productforums.google.com/forum/#!topic/chromebook-central/tJ6LqVMsYxc I verified the issue. I will submit a feedback report with the label #partial_screenshot
,
Apr 27 2018
,
May 16 2018
,
May 19 2018
It is now working erratically again. Sometimes I get a full screenshot, sometimes only a partial one. Feedback just sent with reference to this crbug.
,
May 19 2018
#CBC-RS/TC-watchlist
,
May 25 2018
Links to Feedback Reports submitted (with logs): - https://listnr.corp.google.com/report/85455314028 - https://listnr.corp.google.com/report/85455296076
,
Jun 1 2018
Adding the conops Chrome OS hotlist for tracking.
,
Jun 5 2018
Katie, could this be related to eventfilter priority changes? I see ScreenshotController adding an eventfilter: https://cs.chromium.org/chromium/src/ash/utility/screenshot_controller.cc?type=cs&q=mousecursoreventfilter&sq=package:chromium&g=0&l=288
,
Jun 5 2018
I don't think so: the ordering of the EventHandler processing *should* not have been changed, I was attempting only to change the way the functions looked. Referenced change: https://chromium-review.googlesource.com/c/chromium/src/+/967358 Let me know if you'd like me to investigate further.
,
Jun 6 2018
Looks like my change landed in M67 as well, so it must not be related to that. You could try setting the EventHandler at priority kAccessibility to see if it makes it more reliable?
,
Jun 26 2018
,
Jun 29 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jim.dantin@chromium.org
, Apr 23 2018