Closed Bug 510771 Opened 15 years ago Closed 14 years ago

CSS Problem for margin-right

Categories

(Core :: CSS Parsing and Computation, defect)

1.9.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: manish, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080317 Fedora/3.0.13-1.fc10 Firefox/3.0.13
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080317 Fedora/3.0.13-1.fc10 Firefox/3.0.13

We have 2 machines on Linux and 2 machines on Windows. one machine having 3.5 (XP) and another machine having 3.0.13 (XP) and both linux machine having 3.0.13 and 3.0.12 respectively. Problem is that when we give margin-left for any specific tag inside another div tags then it shows different margin as compare of windows. In linux its shows less margin than windows.

Reproducible: Always

Steps to Reproduce:
We have seen the behaviour on local machine. so can't show you as of now.
We have seen same problem with margin-left as well as compare to windows and linux FF.
What units were you using?  Different units (pt vs. px vs. em) might have different ratios on different machines, because they're measuring different things.
Issue is attended very late. It was px. now its almost 6 months back and machine have upgraded to fedora 12. If this issue have been taken on table instantly then I might make more light on it.
Sorry, I stumbled upon this bug while going through Core bugs (in particular, those with "CSS") that are languishing in Firefox::General.  It would have been seen sooner if filed in a different component.

Since I don't think there's enough information in this report to do anything about it, marking as INCOMPLETE, but feel free to reopen if you have more information.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Component: General → Style System (CSS)
Product: Firefox → Core
QA Contact: general → style-system
Resolution: --- → INCOMPLETE
Version: unspecified → 1.9.0 Branch
You need to log in before you can comment on or make changes to this bug.