Browser Interpretation

	Home Register Search Help Login

Recent Posts
Todays Posts
Most Active posts
Posts since last visit
My Recent Posts
Mark posts read

Sponsors
Shopping Cart Software
Ecommerce software integrated into Frontpage, Dreamweaver and Golive templates. No monthly fees and available in ASP and PHP versions.
Website Templates
We also have a wide selection of Dreamweaver, Expression Web and Frontpage templates as well as webmaster tools and CSS layouts.
Frontpage website templates
Creative Website Templates for FrontPage, Dreamweaver, Flash, SwishMax

Browser Interpretation

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> Web Development >> Cascading Style Sheets and Accessibility >> Browser Interpretation

Page: [1]


shellaire Posts: 5 Joined: 1/24/2008 Status: offline	Browser Interpretation - 1/24/2008 21:25:56 Hi! I just started Web Development Training/Schooling about 4 months ago. I have experimented with different languages for years and decided to learn more! ( I hope!) Anyway, I came upon an assignment which I am having trouble answering. I am not looking for someone to give me a direct answer, but if anyone has any suggestions of where I could find the answer that would be great!! The question: How do different browsers interpret padding? How do different browsers interpret margins? I have found many answers and have been looking for hours! But nothing to my complete satisfactory! Help Please! Shelley


Tailslide Posts: 6692 Joined: 5/10/2005 From: Out here on the raggedy edge Status: offline	RE: Browser Interpretation - 1/25/2008 2:29:23 This is actually a pretty complex question - all browsers have different default margins on different HTML items (e.g. paragraphs, lists, divs etc) and many browsers also have different ways of using margin-collapse too - here's a useful page with a load of tests on margin-collapse: http://www.hixie.ch/tests/evil/mixed/collapsemargins.html Plus obviously, there's the IE old box-model issue where it uses it's own, non-standard box model when in Quirks mode. The thing is - as a designer, I'm aware that they're all different in the way they handle these issues but I couldn't list all the differences for you - mainly because my sole issue is getting rid of the differences. So I always use a full DOCTYPE to ensure standards mode across all browsers (or as close to it as IE will allow) and I always use a CSS reset to remove the vast majority of margins and padding defaults so that I'm starting from a level playing field. I think that removing these defaults (or resetting them so that they're all pretty much the same) is more important than necessarily defining the difference from a designing/developing point of view. _____________________________ Little Blue Plane Web Design \| Land Rover project (in reply to shellaire)


shellaire Posts: 5 Joined: 1/24/2008 Status: offline	RE: Browser Interpretation - 1/25/2008 10:11:38 Thank you for the explanation. I , in my research have found most of the answers you posted. You added some extra insight as well. (in reply to Tailslide)

Page: [1]

All Forums >> Web Development >> Cascading Style Sheets and Accessibility >> Browser Interpretation

Page: [1]

Jump to: 1

New Messages	No New Messages
Hot Topic w/ New Messages	Hot Topic w/o New Messages
Locked w/ New Messages	Locked w/o New Messages

Post New Thread

Reply to Message

Post New Poll

Submit Vote

Delete My Own Post

Delete My Own Thread

Rate Posts