Hello,
I think... I find HTML lacking for "software enginering" purposes.
It would/could be great if future versions of HTML get some kind of Diagram
Support, for drawing all kinds of diagrams, like boxes, tables, tables in
tables, boxes in boxes, arrows, lines, arcs, colors, etc, maybe even pseudo
code diagrams
Maybe then we "software engineers/programmers" could work more jointly
together via the web more easily and better !
(Or express our idea's/algorithms/data structures better
)
Sorry I am late, but I could not post to alt.html for about 2 days.
I fixed all the css errors but one which (a) has nothing to do with
the home page elements, and (b) might be some issue with the w3
validator. The "word-wrap" element is properly called in CSS3
according to this:
http://www.css3.com/css-word-wrap/
I put back the word wrap properties (four times) as removing made no
difference and it seems to be valid.
Regarding the html error, I'm not sure why it is invalid. Removing
that too did not make any difference. The "error"is for something
completely unrelated (the logo).
Even with validation, Safari is pushing off those login buttons way to
the right for a reason I cannot explain.
Your page seems to be changing, likely because you are working on it.
I got a version that had several validation errors. Some image tags
were not properly self-closed for xhtml, and this seemed to cause some
confusion with <a ...> and </a> when the img tag was between them.
Also you mentioned that the page worked as intended on IE. That alone
tells me the page is not being served as xhtml, since IE will not work
on xhtml that is properly served. The w3c validator will validate a
page as xhtml, if asked, no matter how it is served. However if you
select verboise output, the validator tells you that your page is
being served as ordinary html which uses text/html. To serve it as
xhtml, you have to associate something other than .html , such
as .xhtml, with the mime type application/xhtml+xml on the server.
Then if you serve the page properly as something.xhtml you will find
IE browsers will not work. To get them to work you have to use header
exchange or something else that will determine if the browser will
accept true xhtml served properly. Then the page is converted to html,
such as 4.01 strict for IE, for example. This can be done using some
rather complicated php in the header exchange. Since you are serving
the page as html, writing the code in xhtml serves no purpose unless
you intend to set up your server to serve true xhtml with the proper
mime type for it. And if you want IE browsers to see the page, you
will have to do something to serve html for them.
Since your page is only being served as html (validate using "more
options" and select verbose output - you find the mime type text/html
is being used), the page is only being parsed as html when you call
the page. However if you serve as true xhtml with mime type
application/xhtml+xml, the page will be parsed as xml. This varies a
bit for different browsers, but even a single error often will bring
up an error report rather than a view of the page. The xml parsers are
about as strict as a mother superior in a convent in the 1800s.
If you properly served your page as true xhtml, it is likely that no
browser would work as the page now stands. The likely outcome is that,
when the xml parser detects the first xml error, it would output an
xml error message rather than a view of the page.
The w3c validators have been known to make an error, but this usually
is corrected soon. In my case I usually find the error is mine. In
any case, you need to try to get rid of all html and css errors first.
Since your page is fairly long, I and likely some others do not have
the time to check the complete page in minute detail.
