-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use noVNC via patternfly-react #8894
Use noVNC via patternfly-react #8894
Conversation
e579cd6
to
051f913
Compare
331c15b
to
ebaab76
Compare
Rebased, since #8402 and patternfly/patternfly-react#288 changed |
ebaab76
to
4225c4d
Compare
This requires full |
4225c4d
to
c8a200a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebased to fix conflicts. I tested the serial and the VNC console, and they both work fine. Thanks!
Looks like this breaks testInlineConsole, this probably changed identifiers and such which needs to be adjusted in the tests. |
c8a200a
to
d9f746d
Compare
Leverage reusable component wraping noVNC. Closes cockpit-project#8894
Reference on old noVNC (prior 1.0.0 introduced newly by patternfly-react) is removed.
Adjusted the tests. |
Leverage reusable component wraping noVNC. Closes #8894
Leverage reusable component wraping noVNC. Closes cockpit-project#8894
The in-browser VNC component is externalized to patternfly-react for it's wider reuse by other projects.
With this change, the noVNC dependency version is updated to
1.0.0
from recent0.6.2
.Checklist:
VncConsole
in patternfly-react); increase patternfly-react version accordinglyVncConsole
componentReact
instead ofreact-lite
since later versions of patternfly-react require it (i.e. use of<Fragment>
)