[jira] [Commented] (GUACAMOLE-125) Sometimes session is not initialised on Full screen

[Nick Couchman (Jira)]

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

Nick Couchman commented on GUACAMOLE-125:
-

This was actually fixed in the unreleased FreeRDP 1.2 version, I believe, but I 
was trying to resolve it with earlier FreeRDP versions.  I'm more than happy to 
cross it off the list!

> Sometimes session is not initialised on Full screen 
> 
>
> Key: GUACAMOLE-125
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-125
> Project: Guacamole
>  Issue Type: Bug
>Affects Versions: 0.9.9, 0.9.10-incubating
> Environment: Guacamole running on Debian 8.6
> Forwarding a windows 2012 R2 session
>Reporter: Frank Giroud
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: fj1.png, fj2.png, fj3.png, fj4.png, fj5.png, fj6.png, 
> notepad_size_limit.jpg, notepad_size_limit_detail.jpg
>
>
> Sometimes after logging in (which happens to be Full scren) the windows 
> session or the RemoteApp is not launched in full screen.
> In fact it behaves like there were a pseudo-resolution smaller than the 
> required one.
> The browser (Chrome is open in a 1920*1200) but the screen displayed is 
> locked to something like 1024*768 or so. 
> When you click on the Fullscreen button. It open and let a black screen all 
> around in the web browser. .
> -The behavior is the same if you start a windows session , the windows 
> desktop displayed in the web browser is in a 'smaller display' and what 
> remains is black.- Haven't succeed to reproduce after all
> I have succeeded to find a way to reproduce the behavior "kind of" more often.
> In my example i configure notepad++ to be a remoteapp (launch by ||notepad in 
> guacamole )
> # Launch a session through Guacamole => No probleme guacamole can be set in 
> fullscreen (on all the browser window)
> # Unmaximized the application
> # Ctrl-Shift-Alt menu => Disconnect
> # On the guacamole option menu (3 choices) => Reconnect
> # The result => my screenshot



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (GUACAMOLE-918) Guacamole Display not visible under Shadow DOM

[Jonas Zeiger (Jira)]

Jonas Zeiger created GUACAMOLE-918:
--

 Summary: Guacamole Display not visible under Shadow DOM
 Key: GUACAMOLE-918
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-918
 Project: Guacamole
  Issue Type: Bug
  Components: guacamole-common-js
Affects Versions: 1.1.0
 Environment: guacamole-common-js 1.1.0 on Chromium 78
org.apache.guacamole:guacamole-common:1.0.0 on OpenJDK 11

Reporter: Jonas Zeiger
 Attachments: guacamole-display-under-shadow-root.png

The Guacamole display doesn't show when inserted under shadow DOM.

The display is attached like this:

{code:javascript}
const wrapper = this.shadowRoot.getElementById('console-screen-wrapper');
wrapper.style.width = '' + 640 + 'px';
wrapper.style.height = '' + 480 + 'px';
this.display = wrapper.appendChild(client.getDisplay().getElement());
{code}

The display elements including canvas are present in the DOM (see DOM 
screenshot).

The reason seems to be the explicit canvas/layer z-index setup here:

guacamole-common.js, Guacamole.Layer()
{code:javascript}
// Explicitly render canvas below other elements in the layer (such as
// child layers). Chrome and others may fail to render layers properly
// without this.
canvas.style.zIndex = -1;
{code}

Setting canvas.style.zIndex to 0 instead of -1 makes all layers visible under 
shadow DOM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)