Bug 807956

Summary: Forms are inactivated while using Firefox 11 to add new cases.
Product: [Other] TCMS Reporter: Guohua Ouyang <gouyang>
Component: Web UIAssignee: cqi
Status: CLOSED EOL QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: high    
Version: DevelCC: cqi, dli, gouyang, jcai, junzhang, leiwang, mkudlej, ryang, vchen, xkuang, ycui, yuwang
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.7.0-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-26 03:31:51 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 Guohua Ouyang 2012-03-29 08:40:34 UTC 
Description of problem:
Add new case using Firefox 11, the forms "Setup" "Breakdown" "Actions" are not activated to accept the input characters.



Version-Release number of selected component (if applicable):
Firefox 11 on Fedora 16

How reproducible:
100%

Steps to Reproduce:
1.
 
Actual results:

Expected results:


Additional info:
Comment 1 cqi 2012-03-29 11:51:28 UTC 
You can restore or maximize the window or press Alt+F10 temporarily. It seems there is some conflict between the widget and FF 11.
Comment 2 Guohua Ouyang 2012-03-30 02:36:48 UTC 
(In reply to comment #1)
> You can restore or maximize the window or press Alt+F10 temporarily. It seems
> there is some conflict between the widget and FF 11.

it works after maximize the window, thanks.
Comment 3 yawei Li 2012-04-11 03:14:12 UTC 
will be resolved on 3.7.0 release.
Comment 4 Jin Zhao 2012-04-20 08:48:02 UTC 
*** Bug 814603 has been marked as a duplicate of this bug. ***
Comment 5 Xin Gao 2012-04-24 11:51:09 UTC 
Verify version 3.7.0-1 on stage -> PASS

Steps:
open tcms using ff11.
create new case.
type text to setup...

Actual result:
it works well.
Comment 6 Jin Zhao 2012-04-28 02:42:11 UTC 
*** Bug 817031 has been marked as a duplicate of this bug. ***