Closed
Bug 729882
Opened 13 years ago
Closed 13 years ago
Absolute positions of the controls are now based on the container and not based on the HTML page
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: sridharsivam, Unassigned)
Details
Attachments
(1 file)
106.08 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120215223356
Steps to reproduce:
HTML page having controls positioned with absolute position are getting distorted after upgrading to Firefox 10
Actual results:
All the controls are now positioned according to the div enclosed and not the BODY, which should be the case
Expected results:
The controls should get positioned in accordance to the BODY and not with the container
We need a testcase or a link to a live page. Images doesn't give anything to work on.
Reporter | ||
Comment 2•13 years ago
|
||
The code that renders the HTML is not simple and will take little time to create a sample/test case. We are also working on to get a live URL up and running. Once done with either of the options, the details will be shared.
Reporter | ||
Comment 3•13 years ago
|
||
Try accessing the following URL:
http://ec2-50-16-16-51.compute-1.amazonaws.com/SDE/
User: USER1
pwd: bmc!2
Once logged in, click on the blue 'Workspaces' bar on the left hand side. From the 'Incident Management' header, click on the 'Incidents (ITIL)' link to bring up the form. Look at the control positions on the right hand side.
This is a side effect of bug 10209 - which has been fixed in Firefox 10.
However, the real issue is within your software. Depending on the browser it encounters, it defines different 'top' and 'left' values for the absolutely positioned tables inside the element #SECTBL_1SectionTabContent. Apparently to overcome the bug Firefox had.
These values are no longer correct because the Firefox bug is gone.
Note: Incorrect values are also sent to Google Chrome users.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•