[ 
https://issues.apache.org/jira/browse/GUACAMOLE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350789#comment-16350789
 ] 

Michael Jumper commented on GUACAMOLE-498:
------------------------------------------

This is actually an issue with Chrome's handling of HiDPI vs. the interpolation 
it performs on scaled graphics. When the desktop is scaled to that degree, it's 
not Guacamole which handles the rendering at the device's native resolution, 
but Chrome and its rendering backend. Those 1-pixel lines are regions which are 
not being correctly updated by Chrome, despite Guacamole updating the graphical 
area which corresponds to those regions.

> Guacamole (RDP) on Chrome on HiDPI screen produces some artifacts
> -----------------------------------------------------------------
>
>                 Key: GUACAMOLE-498
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-498
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP
>    Affects Versions: 0.9.14
>         Environment: Windows 10 (1709/10.0.16299.192)
> Google Chrome 64.0.3282.140
>            Reporter: Vasco Freire
>            Priority: Minor
>         Attachments: guacamole01.png, guacamole02.png
>
>
> When using Guacamole to connect to a Windows RDP server, using Google Chrome, 
> on a computer with a HiDPI screen (3200x1800, 200% scaling), some artifacts 
> appear, as shown in accompanying screenshots.
> Screenshots show an application (Notepad - but other apps show this problem) 
> with either horizontal or vertical 1-pixel lines between areas where the 
> screen is updated.
> On the first screenshot, the mouse cursor was moved vertically, causing 
> different menu entries to be selected, causing the horizontal lines. On the 
> second screenshot, text was written, causing the vertical lines between the 
> characters, as they appeared.
> This problem does not occur on other browsers (Firefox, MS Edge) or other 
> operating systems (Chrome on Linux).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to