>> I would also suggest that when the new site is being made that it is 
modeled for compliant browsers first then add the necessary tweaks for 
IE, seems to make things a lot easier

Depends...
Personally, I'm using an MSIE emulator for FF. (see 
http://webfx.eae.net/dhtml/ieemu/ )
MSIE has very convenient features missing in the standard.
Thanks to __defineSetter__ and __defineGetter__ methods, one can define 
new properties in Mozilla equvalent
to the MSIE properties.
Sticking to the standard is very nice, in theory, the problem is when 
the standard is dumb, you restrict yourself
to dumb functionalities.

Just an example, the width, top, left etc. properties contain strings 
(ie. "100px"), not really convenient for calculations in a program.
MSIE has added the pixelWidth, pixelTop, pixelLeft etc properties, that 
contain integer values that you don't have to parse.
For instance the following declaration in Mozilla creates a  pixelWidth  
property  in Mozilla.
You don't even have to test for the browser in the code.
CSSStyleDeclaration.prototype.__defineGetter__("pixelWidth", function() {
return parseInt(this.width) || 0;
});

-- 
_______________________________________
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address: [EMAIL PROTECTED])
Thanks.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:198389
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to