2 questions; CSS Mobile 1.0 & weird form bug

[tom_moonen]

hello all, this is my first post here and already i can ask two questions, how great is that? :rolleyes:


My first question;
I'm recreating my string quartet's website after a long period of negligence. After some reading-up on webdesign, i came with a few conclusions and a few questions as well.

First I should implement CSS and xhtml for the site's structure and layout.
But which CSS profile to choose (i use TopStyle Pro atm). CSS lvl.1, lvl.2 or Mobile 1.0?

As the sound and image quality off mobile appliances are inferior to a pc's or or laptop's, i shouldn't be overly concerned about the accessibility for mobile systems. However, it would be handy if our audience (or the members of my quartet) could for instance find the adress and itinerary of our performance location whilst on the road.
CSS lvl.2 has more functionalities than lvl 1, but is not so commonly accepted, i presume.

esteemed reader, what is your opinion?


My second question is; what could have caused a weird form bug i'm experiencing?
The form is on my string quartet La Dolce Vita's website (http://www.c-moonen.demon.nl/schrijfons.html)

I don't know what causes it but when i try to fill in the form with one of my two computers (on the same DSL connection), the one that i used to upload the file doesn't get the form correctly processed (error message to be found below). The other computer gets all the form's data processed and delivered to my email inbox. They both run on 2000Pro and have the same IE version, so how weird is that? And what might cause this difference? Is 50% or more of the website's public unable to send me feedback by mail?

Here's the error message i get on the faulty computer:
X-Error: No HTTP_REFERER
Form submission error
There was an error in submitting the form. If this condition persists, please mail our support department.
Thank you.

[tom_moonen]

oh yeah, the form is in dutch, as is the rest of the site.

That shouldn't put you off though, it's a feedback form which asks people for their name, email adress and feedback. Zend=Send, Wis=erase.
And i don't like the colours either :)

[Fang]

Go for HTML4 strict with seperate CSS for screen and mobile.

The mailform is tring to get the referer, which is not always available.

[tom_moonen]

thanks...why not xhtml if i may ask?

and the weird thing is it <u>allways</u> happens to the computer i use most, and never to the other. so i think it's something else. maybe some security issue?

[Fang]

http://www.alistapart.com/stories/betterliving/
http://www.hixie.ch/advocacy/xhtml
Adding a XHTML DTD does not make it XHTML (http://validator.w3.org/check?verbose=1&uri=http://www.c-moonen.demon.nl/schrijfons.html)

The mailform should not throw an error if the referer is not available
From PHP manual'HTTP_REFERER'
The address of the page (if any) which referred the user agent to the current page. This is set by the user agent. Not all user agents will set this, and some provide the ability to modify HTTP_REFERER as a feature. In short, it cannot really be trusted.

[toicontien]

But which CSS profile to choose (i use TopStyle Pro atm). CSS lvl.1, lvl.2 or Mobile 1.0? ... CSS lvl.2 has more functionalities than lvl 1, but is not so commonly accepted, i presume.
CSS 2.0 is more supported than 1.0? Mm. Ish. Internet Explorer 5.01 up to the latest version on Windows, as well as 5.0 - 5.2 on Mac, supports enough CSS 2.0 to enable you to use CSS 2.0 as a design choice. Firefox, Opera, Safari and Omniweb all support CSS 2.0 extremely well -- better than Internet Explorer. Internet Explorer 7 (set to be released in the next several months) is already shooting for better standards compliance to CSS 2.0. There are dozens of spin-off browsers using the most popular rendering engines, like KHTML (Safari, mac os) and Gecko (Firefox/Netscape/Mozilla, windows, mac os, *nix).

That covers about 99% of the browsers used today. CSS 2.0 (in revision 2.1 now) is perfectly fine to use on Web pages as the primary design method.

And CSS allows you to specify different style sheets for different media. You might shoot for screen (desktop browsers), print, and handheld style sheets.