Bug 1796626

Summary: topology create connector marker inconsistently changes shapes
Product: OpenShift Container Platform Reporter: cvogt
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: low    
Version: 4.4CC: aos-bugs, gamore, nmukherj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:28:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
connector is in the empty space
none
when connector is on the node none

Description cvogt 2020-01-30 19:30:10 UTC 
Description of problem:
There are two connector markers that are shown when creating a new connector in topology:
- an arrow when drawing a connection between two nodes
- a + sign when drawing a connection to an empty space in the graph or an application grouping

The following scenario causes the connector marker to jump between the two marker types. This isn't a big issue because the correct action is still executed, however it is a visual flaw.

Steps to Reproduce:
1. a node in topology
2. from one node, begin dragging the create connector handle
3. drag away from the node

Actual results:
While moving the cursor quickly, the connector end marker switches between an arrow and a plus sign

Expected results:
If the connector handle is over the empty space in the graph, it should always be a plus sign. No matter how quickly the cursor is moved.
Comment 2 Gajanan More 2020-03-04 07:25:11 UTC 
Created attachment 1667407 [details]
connector is in the empty space
Comment 3 Gajanan More 2020-03-04 07:25:46 UTC 
Created attachment 1667408 [details]
when connector is on the node
Comment 4 Gajanan More 2020-03-04 07:26:19 UTC 
I have validated this bug on 
Build: 4.4.0-0.ci-2020-03-03-151622
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.
Comment 6 errata-xmlrpc 2020-05-04 11:28:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581