Results 1 to 5 of 5
  1. #1

    HTML & CSS Frequently Asked Questions

    If you have input on the questions already in the FAQ or want to suggest a new question for someone to write an answer to, please post here.

  2. #2

  3. #3

    HTML & CSS Frequently Asked Questions


  4. #4

    HTML & CSS Frequently Asked Questions

    • saf:
      Apple Safari (based on KHTML and KJS by KDE) <>, Mac OS X
    • konq:
      KDE Konqueror. <>, X11
    • opn:
      Opera. Normally we're talking about version 7 on Windows and Linux, but we may be talking about version 6 for the Mac. <>, Windows, Linux, (Mac).
    • nsn:
      Netscape6, Netscape7. Netscape browser based on Mozilla.
    • nnn:
      Netscape Navigator. Netscape browsers up to version 4.x.
    • ncn:
      Netscape Communicator. Same as nn4.x.

  5. #5

    HTML & CSS Frequently Asked Questions

    • Nearly every tag has a meaning. <h1> means the main title of a page, <em> means emphasised text. Correct application of these meanings is extremely advisable practice in today's Web. Why? That's a little more complicated. XML (which XHTML is based on), SGML (which HTML is based on) and therefore their derivatives are all markup languages. This is a special way of describing data &mdash; with tags.

      Each tag describes the data contained with it. <em> means that the text inside is slightly more important. If we used, say, <cite> to achieve the same presentational effect, we're saying that the data inside was quoted, or cited, from somewhere else, when it's not. In the same way, if we use tables to lay out our page, we are describing this data as tabular. It's not. This undermines the very purpose of HTML, XHTML, or whatever markup language we're using.
    • Second reason: tables are presentational. XML, which is really the new markup standard, dictates that all presentation should be removed from style! This means not using presentational tags like <b> or <font> in our XHTML, but instead using CSS to achieve this presentation. This makes sense &mdash; our code becomes lighter, the same presentational code can be cached for the entire site meaning faster loading times, and when something like a webpage to braille converter comes along, it won't be confused (how can braille be bold? Chances are you want strong emphasis, <strong>, or you want to make something a header, <h1>, <h2>, <h3> ... <h6>).

      Also, if we have an 'inferior' rendering device like a PDA or mobile phone (cell phone), we can present to them the unstyled XHTML, which will be perfectly legible. Tables can screw up a design on such small resolutions.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts