Bug 719427

Summary: Clicking on things with chrome isn't reliable
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: WebUIAssignee: Adam Price <adprice>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.1CC: mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-17 14:12:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Justin Sherrill 2011-07-06 19:36:50 UTC
Currently in katello with chrome clicking on things isn't very reliable.  It seems to have to do with whether your mouse moves any while you are clicking.  If it stays completely still the click will work.  If it moves a couple of pixels during the click, nothing happens.

Need to investigate.

Comment 1 Justin Sherrill 2011-07-14 12:48:03 UTC
After talking to jrist, we figured out that it was our fake buttons that were causing issues.  The issue only happens with divs or spans as buttons.  With 'real' buttons they work just fine.


For now:  convert existing buttons to real buttons

for the promotion page sliding tree: create a system where we track mousedown/mouseup and make sure it is on the same element.

Comment 2 Justin Sherrill 2011-07-14 13:00:38 UTC
example of doing a simple button:

 %input{:type => "button", :class => "button", :id=>"save_role_button", :tabindex => "2", :value=>"#{('Save Role')}"}

Comment 3 Mike McCune 2011-08-01 22:47:48 UTC
Just a note, still have the fake buttons on the Provider Products and Repos page.

Comment 4 Mike McCune 2012-01-26 19:38:21 UTC
mass move to CFSE product.

Comment 5 Jordan OMara 2012-02-27 20:22:15 UTC
Justin filed a bug against chrome here: http://code.google.com/p/chromium/issues/detail?id=89317

Comment 7 Mike McCune 2013-08-16 18:19:23 UTC
getting rid of 6.0.0 version since that doesn't exist