Nick Cowie wrote:
Katrina
I would serve XHTML and stick to XHTML-Basic or XHTML-MP subset of
features.
Gday Nick,
Thank you for your response :))))
Which accompanying mime type would you choose for XHTML-Basic?
text/xml
application/xhtml + xml
application/xml
Note: XHTML-MP has it's own mime-type
application/vnd.wap.xhtml+xml
If you pick XHTML-MP and its associated mime type, then it would be a
special mobile site, and wouldn't you also need to use content
negotiation to ensure user-agents that couldn't handle that mime type be
redirected?
Because not all elements are available in XHTML-Basic or XHTML-MP for
example button. So if you build a form use input type="submit" not button
type="submit" otherwise most mobile users will not be able to submit the
form. And only use the WCSS (Wireless CSS) standards you should get most
modern phones.
Would it be smart to make your whole site like this anyway, so you serve
the same content to everyone?
If not, how would you then determine whether or not incoming traffic was
mobile and thus to be redirected to a subdomain that served up required
content?
Kat
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
