Closed Bug 264593 Opened 20 years ago Closed 20 years ago

changing styles at the DOM level does not work.

Categories

(Firefox :: Tabbed Browser, defect)

Product:
Firefox
Component:
Tabbed Browser
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jim, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

I create all my web page code dynamically, and that includes the dynamic
positioning of elements. when trying to position the elements with
obj.style.pixelLeft or any of the other properties, the object stays in the
upper left corner. works fine on all version of IE that I have.

Reproducible: Always
Steps to Reproduce:
run this html and see the edit box will be in the upper left corner, not 100
pixels in and 100 pixels down.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Hello</title>
</head>
<body>
<script type="text/javascript" LANGUAGE="Javascript">
obj = document.createElement("INPUT");
obj.style.position = 'absolute';
obj.style.pixelLeft = 100;
obj.style.pixelTop = 100;
obj.style.pixelWidth = 200;
obj.style.pixelHeight =15;
document.body.appendChild(obj);
</script>
</body>
</html>
That's a textbook case for my method of cross-browser property/method research:
google pixelLeft, first result is msdn (strike one) which says "There is no
public standard that applies to this property." (strike two) and it doesn't work
(strike three). Then, google pixelLeft site:mozilla.org and you get two pages
explaining what to do instead.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
since this is the second item that I have posted that has turned out to not be 
a DOM spec and FireFox is not going to support it, then I am going to assume 
that FireFox is not going to support any property that is not in the official 
WC3 spec. 
The suggestion on the Google search did reveal a very handy DHTML library that 
is working quite well. The unfortunate part for me is that our application is 
mostly written and runs great on IE. We wanted to support more browsers. Now I 
have to re-write about 60% of the code. But I guess I have to do what I have to 
do if I want to run on FireFox. 
Thanks for the Google suggestion.
You need to log in before you can comment on or make changes to this bug.