ISSUE-164: CONTENT_FORMAT_SUPPORT

CONTENT_FORMAT_SUPPORT

State:

CLOSED

Product:

mobileOK Basic tests

Raised by:

Jo Rabin

Opened on:

2006-10-26

Description:

While there has been a lot of discussion about IE not accepting a/x+x there has
been no discussion of the fact that Firefox barfs on it too - UNLESS you specify
the html namespace as the default namespace in the root element (this is
actually required for a conforming doc). Opera too has a problem if the
namespace is missed out. So I think that this should appear in our XHTML
validity test.

Both Firefox and IE barf on application/vnd.wap.xhtml+xml. But Opera eats it up
- with or without a namespace.

My suggestion is that we add a test for the presence of the namespace and WARN
if absent.

Incidentally the validator at W3 doesn\'t seem to care whether it is there or not.

Related Actions Items:

No related actions

Related emails:

1. [minutes] Thu 14 teleconf (from dom@w3.org on 2006-12-21)
2. Re: ACTION-370 Summarise current issues around Content-Type, DOCTYPE, Character Encoding ... and more besides. (from andrea@trasatti.it on 2006-11-20)
3. RE: ACTION-370 Summarise current issues around Content-Type, DOCTYPE, Character Encoding ... and more besides. (from jo@linguafranca.org on 2006-11-20)
4. Re: ACTION-370 Summarise current issues around Content-Type, DOCTYPE, Character Encoding ... and more besides. (from srowen@google.com on 2006-11-20)
5. Re: ACTION-370 Summarise current issues around Content-Type, DOCTYPE, Character Encoding ... and more besides. (from srowen@google.com on 2006-11-17)
6. Re: ISSUE-164: CONTENT_FORMAT_SUPPORT (from srowen@google.com on 2006-11-10)
7. Re: ISSUE-164: CONTENT_FORMAT_SUPPORT (from dom@w3.org on 2006-10-27)
8. ISSUE-164: CONTENT_FORMAT_SUPPORT (from dean+cgi@w3.org on 2006-10-26)

Related notes:

Display change log