Bug 1373145 - Provision Instances view is always broken in Chrome with Grammarly extension
Summary: Provision Instances view is always broken in Chrome with Grammarly extension
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: 5.7.0
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-05 10:52 UTC by Ievgen Zapolskyi
Modified: 2018-04-19 16:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-15 12:43:42 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
exception (11.87 KB, text/plain)
2016-09-05 10:52 UTC, Ievgen Zapolskyi
no flags Details

Description Ievgen Zapolskyi 2016-09-05 10:52:00 UTC
Created attachment 1197871 [details]
exception

Description of problem:
All the tabs except first one are empty (exception from production.log is attached) in Provision Instances view when Grammarly extension is enabled in Chrome

How reproducible:
~ 90 %


Steps to Reproduce:
1. Install Grammarly extension for Chrome and enable it
2. Open appliance in Chrome
3. Open any provider on Instances view (f.e. Compute->Clouds->Instances)
4. Click Lifecycle->Provision Instances
5. Choose any image in the "Provision Instances - Select an Image" dialog and click Continue
6. Try to click Purpose or Catalog tabs in Provision Instances view

Actual results:
All the tabs are empty except Request one. Provisioning is impossible.

Expected results:
1. Grammarly extention should not affect Provisioning in CFME.
or
2. Add some information to CFME documentation that some Chrome extensions can cause such issues. So people have to try to disable extensions first if they experience similar issues.

Comment 2 Dave Johnson 2016-09-15 12:43:42 UTC
Closing this one, don;t use that extension.  I don;t think we can expect to support any and every browser plugin.  In terms of this one, is there a good reason why we should Ievgen?

Comment 3 Ievgen Zapolskyi 2016-09-16 13:40:56 UTC
Although, this extension is quite popular. I don't see any substantial reason to support this extension. But I had to raise this because customers may come across such issue in future.


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