Pescador:

I think I understand relevance of ... "I already use w3c and some problems appears" so I can offer a comment on that:
Mozilla and IE (at least pending the next vers of IE) and <insert almost any other browser name here> STILL don't use the same Document Object Model (DOM) AND probably even more relevant to your variant renderings question, support CSS differently.

These are a few among many ways to deal with this:

• acquire an exhaustive understanding the cross browser quirks
• accept (for a base testbed) some version of some browser, validate the html and css, and then tweak code for other target browsers until you can live with the results across the board
• code a 'browser check' into each page, and create a mechanism to output code suited to each browser based on the check.

While the first might be admirable, in some fashion or another, it might require commiting 100% of your time and thus would fail as a goals-oriented approach. However, a less-than-exhaustive understanding can save you a lot of trouble.

So too can the second, though it can also spiral into "never-finished-hell"

And three is fine, presuming the restrictions on your work don't do battle with browser-checking (for ex: the site of one of my clients has to conform to rules that interpret US and w3c Accessibility Standards as banning javascript and is also restricted by host-imposed limits on alternate approaches) and so long as you can deal with browser quirks by using .css -- ie, without creating redundant pages for each browser.

And if the rest of your post means you're working on a project of which you fear the Monks will disapprove -- sobeit, but the editorial content isn't the issue; it's the code. Feel free to compress, redact, <snip> anything not relevant to the question at hand.

    ww, ex-schodckwm

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.