Bug 1295453 - Update Platform Matrix regarding Google Chrome and VMRC
Summary: Update Platform Matrix regarding Google Chrome and VMRC
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.6.0
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard: doc
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 14:47 UTC by Marianne Feifer
Modified: 2016-03-15 14:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-15 14:52:04 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 1548913 0 None None None 2016-01-04 14:47:57 UTC

Description Marianne Feifer 2016-01-04 14:47:57 UTC
Description of problem:

From BMcLaughlin

I believe you're the go-to person to get documentation updated.  If not, please feel free to send me a snarky reply referencing the correct person.  :)  Enjoy your time off!  :)

Need to update the browser support for Google Chrome.

---

tldr;
All new versions of Chrome do not support VMRC consoles effective 9/1/2015.

---

Detailed version:
Google Chrome disabled NPAPI plug-in support by default starting at version 42.0.2311, which was released on April 4, 2015.  To enable NPAPI plug-ins in this version of Chrome users had to visit [1] and re-enable the browser functionality.

Google Chrome removed support for NPAPI plug-ins in version 45.0.2454, which was released on September 1, 2015.

[1] chrome://flags/#enable-npapi


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 2 Andrew Dahms 2016-02-24 13:51:24 UTC
Hi Marianne,

Looks like the change for this one has already gone in to the KBase - would it be ok to close this bug?

Kind regards,

Andrew

Comment 3 Marianne Feifer 2016-03-15 14:52:04 UTC
Yes.


Note You need to log in before you can comment on or make changes to this bug.