![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Animesh Kumar wrote: I was checking my page in IE and Mozilla and the results were nice so far. http://www.stutimandal.com/gif_misc/vishnu_vandanam.htm Hmmm... try it in mozilla again, but this time zoom text up a notch or two. The layout is rather broken. BTW, you probably don't realize you haven't set a body background color. My browser default, which is not white, shows through. It is not very attractive. |
#3
| |||
| |||
|
|
I have launched a testing phase of my website on sanskrit poetry. It uses CSS and HTML only, so far. I was checking my page in IE and Mozilla and the results were nice so far. Yesterday I happen to check the page in Opera and the result was awful :-( http://www.stutimandal.com/gif_misc/vishnu_vandanam.htm Can someone suggest if there is something wrong with the CSS or is it just Opera? |
#4
| ||||
| ||||
|
|
Animesh Kumar <animesh1978 (AT) gmail (DOT) com> wrote: I have launched a testing phase of my website on sanskrit poetry. It uses CSS and HTML only, so far. I was checking my page in IE and Mozilla and the results were nice so far. Yesterday I happen to check the page in Opera and the result was awful :-( http://www.stutimandal.com/gif_misc/vishnu_vandanam.htm Can someone suggest if there is something wrong with the CSS or is it just Opera? Given the subject line you seem to have already made up your mind. |
|
Your doctype triggers quirks mode in most browsers. You should use strict coding with a matching doctype, dump the mixup between XHTML and HTML and the <center> and <font> crap. |
|
A document should be structured with at least one header, they should not be used to select a font size, but in an hierarchical and successive manner. |
|
Opera centers the "midcol", since you've not positioned it this is perfectly normal behaviour. |
#5
| |||
| |||
|
|
Animesh Kumar wrote: http://www.stutimandal.com/gif_misc/vishnu_vandanam.htm Can someone suggest if there is something wrong with the CSS or is it just Opera? Neither -- your HTML. |
|
Ditch the big <center>...</center> element wrapping the whole page and find some other way of centring the content on the page (perhaps using auto-width margins?) |
#6
| |||
| |||
|
|
Animesh Kumar wrote: http://www.stutimandal.com/gif_misc/vishnu_vandanam.htm Can someone suggest if there is something wrong with the CSS or is it just Opera? Neither -- your HTML. Ditch the big <center>...</center> element wrapping the whole page and find some other way of centring the content on the page (perhaps using auto-width margins?) |
#7
| ||||
| ||||
|
|
Your doctype triggers quirks mode in most browsers. You should use strict coding with a matching doctype, dump the mixup between XHTML and HTML and the <center> and <font> crap. I see, so your reply suggests me that <center> is not suitable in HTML. |
|
I am looking at the w3.org site to find out which tags are allowed in HTML. Btw, does this mean XHTML supports <center> tag? The font tag was introduced in a jiffy. I will look again at it. |
|
A document should be structured with at least one header, they should not be used to select a font size, but in an hierarchical and successive manner. Sorry, I didn't get your point here. |
|
PS: any good tutorial on positioning? |
#8
| ||||
| ||||
|
|
Animesh Kumar <animesh1978 (AT) gmail (DOT) com> wrote: snip Nor any other type of presentational markup. HTML should be used to structure and semantically mark up content. Styling such as alignment should be done via CSS. |
|
Use a strict doctype in your documents, you can then run your documents through the w3c HTML validator and it'll throw errors when you use presentational elements. |
|
snip The first header in a document should be an h1, subsections below that should be preceded by h2, subsections of the h2 section should be preceded by an h3 etc. |
| PS: any good tutorial on positioning? Positioning is tricky to get right, budding CSS authors often make the mistake of using positioning before they have the skills to do it right. An example: http://homepage.ntlworld.com/spartanicus/temp.png I'd advice to stay clear of positioning until you are skilled with CSS. |
#9
| |||
| |||
|
|
The first header in a document should be an h1, subsections below that should be preceded by h2, subsections of the h2 section should be preceded by an h3 etc. That's fine. I understand this, but how does it relate to the webpage in question (or rather tatters)? |
|
PS: any good tutorial on positioning? Positioning is tricky to get right, budding CSS authors often make the mistake of using positioning before they have the skills to do it right. An example: http://homepage.ntlworld.com/spartanicus/temp.png I'd advice to stay clear of positioning until you are skilled with CSS. Hmm, I have read the block model, padding etc stuff from Meyer's book. Mostly you learn computer scripting/coding by applying them and I think I am that stage. |
|
Running away from positioning isn't going to help my cause. |
#10
| |||
| |||
|
|
Animesh Kumar <animesh1978 (AT) gmail (DOT) com> wrote: The first header in a document should be an h1, subsections below that should be preceded by h2, subsections of the h2 section should be preceded by an h3 etc. That's fine. I understand this, but how does it relate to the webpage in question (or rather tatters)? The webpage in question contains a sole h2. |
| PS: any good tutorial on positioning? Positioning is tricky to get right, budding CSS authors often make the mistake of using positioning before they have the skills to do it right. An example: http://homepage.ntlworld.com/spartanicus/temp.png I'd advice to stay clear of positioning until you are skilled with CSS. Hmm, I have read the block model, padding etc stuff from Meyer's book. Mostly you learn computer scripting/coding by applying them and I think I am that stage. You are wrong. |
| Running away from positioning isn't going to help my cause. It will, there are few good reasons to resort to positioning, and many drawbacks. Study the flow instead. |
![]() |
| Thread Tools | |
| Display Modes | |
| |