Closed
Bug 779313
Opened 13 years ago
Closed 13 years ago
Weird image positioning
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vampirul_14, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20120731030541
Steps to reproduce:
Access the pages described in the "What Happened" section.
Actual results:
When accessing any of the folowing pages using the current stable version of firefox, the image placement is from css and html is not respected by the browser. This bug is not apparent in the nightly version or in any other browser.
Links:
http://mw2promod.eu/downloads
http://mw2promod.eu/team
http://mw2promod.eu/contacts
Expected results:
The images should be perfectly aligned to one-another. Use the current nightly version to see the proper arrangement of the images in the page.
Reporter | ||
Updated•13 years ago
|
Component: Untriaged → General
Comment 1•13 years ago
|
||
>This bug is not apparent in the nightly version or in any other browser.
In that case the bug is already fixed and there is nothing more to do for us or I'm missing something ?
Note to other triagers: I will mark this wfm after the reporter commented.
Component: General → Untriaged
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Matthias Versen (Matti) from comment #1)
> >This bug is not apparent in the nightly version or in any other browser.
> In that case the bug is already fixed and there is nothing more to do for us
> or I'm missing something ?
>
> Note to other triagers: I will mark this wfm after the reporter commented.
Maybe I was not clear enough.
Let me give you an example:
Here is a screen shot with the 14 branch of firefox:
http://gyazo.com/8936e7e9133dc77e12e9bf5223b9dabb
And here is one with the 17 branch:
http://gyazo.com/f2f2b1a52364081dca9cdbf47a2592f9
See how in the 14 branch, the images are not aligned properly like in the 17 one?
Comment 3•13 years ago
|
||
>See how in the 14 branch, the images are not aligned properly like in the 17 one?
Right, i can confirm that but since the issue is already fixed in Firefox17 this means that the bug is already fixed in the source code and will disappear once Firefox17 will be released or probably earlier. That depends when the fix went into the source. You can check Firefox15beta or Firefox16alpha/aurora
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•