Re: XHTML Basic 1.1 and setting input field to numeric mode

> Luca Passani:
> >
> > style="-wap-input-format:'*N'"
>
>   input[type="number"] {-wap-input-format: '*N'}
>
> That WAP stuff doesn't look like style, but behaviour, though (and  
> the value "number" is WF2/HTML5, not XHTMLB1).

I read from http://www.w3.org/TR/xhtml-basic/   :

| [XHTML Basic] is designed for Web clients
| that do not support the full set
| of XHTML features; for example, Web clients
| such as mobile phones, PDAs, pagers,
| and settop boxes. The document type is rich
| enough for content authoring.

now, providing directives to the device about the input format has been 
a feature available on mobile devices since the first HDML phone hit
the market back in 98.
To add to that, XHTML MP was built on top of XHTML Basic 1.0,
with the addition of the  -wap-format property (among others),
which gives an indication of how important this feature is.
Finally, 90%+ mobile devices around the planet support XHTML MP 1.0 
(i.e. the -wap-format property)

Now, how can W3C, in 2008, think they are entitled to create specs 
for mobile devices and, at the same time, blithely ignore such an important feature?

Also, what I gathered from a previous message is that "inputmode='numeric'" will be
 supported by the XHTML 1.1 and XHTML BAsic 1.1 spec. 
Isn't this true anymore?

> "That WAP stuff doesn't look like style, but behaviour"

so what? developers need it and claiming that one intends to create
a markup for mobile devices implies that this feature must be 
supported one way or another. HTML 5 isn't a mobile markup and 
I don't see it becoming a viable one in a 5 years perspective.

I don't know who has created the XHTML Basic 1.1 proposed recommendation, but,
if inputmode="numeric" really isn't supported, I urge them to go back to 
the whiteboard and fix this: this is a feature that has
always been there and developers need it.

Luca

Received on Tuesday, 1 July 2008 08:38:25 UTC