RE: Default Input Mode Warning

Ok...
But I'm still not connecting how this works.  This is an aspx page.  I'm
putting inputmode="latin digits"... however I get the same warning on
those fields, saying that inputmode is not included.  But then I put a
test <input> field on the page that was not a .NET control.  Like this:

<input type="text" name="testing" inputmode="latin digits" />

On this I get a different Error, and this time it is an error not a
warning:

The document is an HTML document and it fails to validate according to
its given DOCTYPE: Attribute "inputmode" must be declared for element
type "input".

So when it is rendered in the checker somehow .NET is stripping out the
inputmode field before it gets to the client maybe.  I say maybe because
when I view the source in IE, or in Firefox I can see that "inputmode"
attribute the same way I can see it on the 'Testing' <input> field.
Note that I'm using this line in the codebehind:

            if (Request.UserAgent.IndexOf("MSIE") == -1)
                Response.ContentType = "application/xhtml+xml";

I do this because IE doesn't recognize that contenttype.  However
Firefox does, so it would seem to me that the source I see on firefox
should be the same that is getting to the mobilechecker.  Someone want
to set me straight?

And of course how do I declare the attribute 'inputmode'?

-----Original Message-----
From: Jo Rabin [mailto:jrabin@mtld.mobi] 
Sent: Wednesday, July 16, 2008 9:37 AM
To: Robert Koernke
Cc: Abel Rionda; public-mobileok-checker
Subject: Re: Default Input Mode Warning

Robert

It is defined here:

http://www.w3.org/TR/xhtml-basic/#s_inputmode

Jo

On 16/07/2008 13:23, Robert Koernke wrote:
> You make it sound like the tag actually needs an attribute 'inputmode'

> as in '<input type="text" inputmode="latin digits"...' - I've tried
that 
> as well, and the checker seems to ignore that attribute, and still
warns 
> with the same.  I googled and googled and did find a site where the
guy 
> put the 'inputmode=' in his source.  But couldn't find any
documentation 
> on it's proper use.  Finally I found using the Style tag with the -wap

> code that I show below.  I thought that was the inputmode it was
looking 
> for.
> 
>  
> 
> -Robert
> 
>  
> 
>
------------------------------------------------------------------------
> 
> *From:* Abel Rionda [mailto:abel.rionda@fundacionctic.org]
> *Sent:* Wednesday, July 16, 2008 4:10 AM
> *To:* Robert Koernke
> *Cc:* public-mobileok-checker
> *Subject:* RE: Default Input Mode Warning
> 
>  
> 
> Hi,
> 
>  
> 
> According to mobileOK test document [1], only inputmode attribute is 
> considered. Furthermore, WAP CSS
> 
> styles are out of scope (only CSS Level 1) .
> 
>  
> 
> [1] http://www.w3.org/TR/mobileOK-basic10-tests/#DEFAULT_INPUT_MODE
> 
>  
> 
> Regards,
> 
> Abel.
> 
>  
> 
>
------------------------------------------------------------------------
> 
> *De:* public-mobileok-checker-request@w3.org 
> [mailto:public-mobileok-checker-request@w3.org] *En nombre de *Robert 
> Koernke
> *Enviado el:* lunes, 14 de julio de 2008 19:22
> *Para:* public-mobileok-checker@w3.org
> *Asunto:* Default Input Mode Warning
> 
>  
> 
> I still get this error:
> 
> 'There is no inputmode attribute on this text entry element'
> 
> |<input class="mobilenumeric" id="tlogin" maxlength="10" name="tlogin"

> size="10" type="text"/>|
> 
>  
> 
> Except the class named above 'mobilenumeric' has:
> 
> .mobilenumeric
> 
> {
> 
>       -wap-input-format: "*N";
> 
> }
> 
>  
> 
> Also I've tested that this works on the mobile device.  Yet why do I 
> still get the above warning?  Because it's in the stylesheet and not 
> actually on the actual tag?
> 
>  
> 
> Robert Koernke
> 
> Application Developer
> 
>  
>

Received on Wednesday, 16 July 2008 14:30:16 UTC