Bug 1378296

Summary: Scope is too wide for field description link in Advanced Search page
Product: [Community] Bugzilla Reporter: yijli
Component: Bugzilla GeneralAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED NEXTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.0CC: huiwang, mtahir, mtyson, qgong
Target Milestone: 5.0Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.0.3-rh9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-12 10:59:51 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:
Attachments:
Description Flags
This field description link function area none

Description yijli 2016-09-22 04:09:19 UTC
Created attachment 1203578 [details]
This field description link function area

Description of problem:
Scope is too wide for field description link in Advanced Search page

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

How reproducible:
always

Steps to Reproduce:
1.Go to Advanced Search
2.Mouse moves to the blank area that behind string ‘Classification‘
3.Please check attachment.

Actual results:
Mouse cursor changes to '?', If press left key, will jump to new page.

Expected results:
Mouse cursor changes to '?' when mouse just handover ‘Classification‘
If move to the blank area that behind string ‘Classification‘, no change for cursor.

Additional info:
This happens to all field description link in the advanced search page

Comment 1 Jeff Fearn 🐞 2016-09-22 04:28:19 UTC
It's pretty standard to have wide hit targets on labels when they are above the widget.

Comment 2 Rony Gong 🔥 2016-09-22 05:54:07 UTC
(In reply to Jeff Fearn from comment #1)
> It's pretty standard to have wide hit targets on labels when they are above
> the widget.

@Jeff, we all like standard, but why can't we limit the clickable function are just limit to the string itself area. 

Sometimes, I want to click the blank area of this page, and I just click the blank area behind these links, then it will jump to another page which isn't expected.

Comment 3 yijli 2016-10-12 07:25:23 UTC
Tested on QA environment(5.0.3-rh9)
Result:Pass