Custom cursor size doubles on hi-res displays in screenshots and screencasts
Reported by
johannes...@flachware.com,
Jan 8
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Visit https://codepen.io/flachware/pen/xmYdQG?editors=0100 2. Use a hi-res (2dppx) display 3. Make a screenshot of the (green) custom cursor What is the expected behavior? The cursor in the screenshot should look the same as in the browser. What went wrong? On macOS the cursor size doubles in the screenshot and the cursor is blurry. Did this work before? N/A Chrome version: 71.0.3578.98 Channel: stable OS Version: OS X 10.14.0 Flash Version: The issue is relevant because it complicates the creation of screencasts of Chromium based applications.
,
Jan 9
,
Jan 9
Safari and Opera behave the same, Firefox does not support the image-set property yet that is needed to define different cursor versions depending on the display resolution.
,
Jan 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 9
"Safari and Opera behave the same" We use the system APIs to create cursors, and so if Safari behaves the same then the issue lies with the screenshotting. What do you use to create screenshots?
,
Jan 9
I can reproduce the issue by using either the Cmd + Shift + 3 shortcut, the 'Take Screenshot' command of Apple Preview, or screencast software like Camtasia.
,
Jan 9
It seems to me that the problem is with the screenshot APIs. Safari and we set cursors via our cursor API, and they display as intended. So the cursor setting APIs are good. All the screenshot software, both first- and third-party, incorrectly shows cursors. Either they're all incorrectly using their APIs (unlikely) or the APIs to get the full cursor information don't exist. My recommendations would be to: 1. File a bug with Apple (bugreport.apple.com) to let them know about the issue with Command-Shift-3. 2. Email Camtasia. They would know exactly what APIs they're relying on, and if the APIs aren't producing the correct result (as you note they are not) then they can also file bugs with Apple with technical detail. There is nothing we can do on our end. We're setting the cursors as correctly as we can.
,
Jan 9
Thank you for looking into this and pointing me in the right direction. |
||||
►
Sign in to add a comment |
||||
Comment 1 by a...@chromium.org
, Jan 8