dotMobimobiThinkingmobiForgemobiReadyDeviceAtlasgoMobi

Posted by goransv2 2 years 22 weeks ago

pic
 goransv2
mobiForge Newbie
Posts: 2
Joined: 2 years ago
[offline]

I have a xhtml-mp 1.2 page that I have tride to validate it with mobiready and got rating 4, but also got this
error:FAIL
Does not validate against XHTML Basic 1.1

FAIL
Does not validate against XHTML Mobile Profile 1.2

WARN
Does not validate against its stated doctype

And in W3C mobile check I got this FORM error:
Line 266, Column 8 — The content of element type "form" must match "(h1|h2|h3|h4|h5|h6|ul|ol|dl|p|div|pre|blockquote|address|hr|table|script|noscript|fieldset)+".

Line 286, Column 8 — The content of element type "form" must match "(h1|h2|h3|h4|h5|h6|ul|ol|dl|p|div|pre|blockquote|address|hr|table|script|noscript|fieldset)+".

My FORM I think is a basic form

and should validate with XHTML-MP 1.2

Does anyone have any sugestions how to proceed ans solve this problem?

Posted by garbetjie 2 years ago

pic
 garbetjie
Mobile Guru
Posts: 70
Joined: 3 years ago
[offline]

Hi goransv2.

Would you be able to provide us with a link to the page, or a sample of the offending HTML? That could help a bit.

Posted by goransv2 2 years ago

pic
 goransv2
mobiForge Newbie
Posts: 2
Joined: 2 years ago
[offline]

Sample:

<!DOCTYPE html PUBLIC "-//OMA//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Cache-Control" content="public" />
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" />
<meta http-equiv="Cache-Control" content="public" />
<title>test - ehStoragePay</title>
<base href="http://test.mobi:9090" />
<link rel="stylesheet" href="includes/css/stylewap.css" type="text/css" charset="utf-8" />
</head>
<body>
<div class="BodyText">
<div class="pgheader">
<!--beginpgheader-->
<a href="test" accesskey="0">0-Home</a>
 
<!--endpgheader-->
</div>
<div class="Highlight"> Select the country you are in<br />
<form action="http://test.mobi:9090/ehStoragePay/index" method="post" >
<select name="changedCountryCode" size="1" id="country">
<option value="af" >Afghanistan</option>
<option value="al" >Albania</option>
<option value="dz" >Algeria</option>
<option value="as" >American Samoa</option>
<option value="ad" >Andorra</option>
 
<option value="ao" >Angola</option>
<option value="ai" >Anguilla</option>
<option value="aq" >Antarctica</option>
<option value="ag" >Antigua and Barbuda</option>
<option value="ar" >Argentina</option>
<option value="am" >Armenia</option>
<option value="aw" >Aruba</option>
<option value="xac" >Ascension Island</option>
<option value="au" >Australia</option>
 
</select>
 
<br/>
Choose your language <br/>
<select name="language" size="1" id="language">
<option value="en" selected="selected">English</option>
</select>
<input type="submit" value="Change" class="button" />
</form>
</div>
<div class="Highlight">
Call this phone number:<br/>
<a href="wtai://wp/mc;09090245240">0909 024 5240</a>
 
<br />
<br />
and hear your password.<br/>
<br />
</div>
<div class="Highlight">
<form action="http://test.mobi:9090/ehStoragePay/doPay" method="post" >
Enter the password/token that you hear in the phone call.<br/>
<input type="text" name="Token" class="text" maxlength="14" alt="Enter the password/token that you hear in the phone call." />
<br/>
<input type="hidden" name="Id" value="6" />
<input type="hidden" name="countrycode" value="gb" />
<input type="hidden" name="language" value="en" />
<input type="submit" value="Access" class="button" />
</form>
 
</div>
<div class="footerng"><a href="test" accesskey="0">0-Home</a></div>
<div class="footer">test.mobi Beta 2009</div>
</div>
</body>
</html>

Posted by garbetjie 2 years ago

pic
 garbetjie
Mobile Guru
Posts: 70
Joined: 3 years ago
[offline]

Hey goransv2.

I took a look at the markup you supplied, and I've managed to track down where the errors are coming in.

One thing I might suggest, is that you use the mobiready tool, in conjunction with the W3 validator. The two together make for a very powerful combination when validating markup.

The problem you're experiencing comes in with some invalid markup that is contained within your pages. As an example, you've got some inline markup that needs to be contained within a block element (<select> directly in a <form> element, with no wrapping <div> or <p>.

If you run the code as-is, through the W3 validator, you'll see some fairly detailed errors coming through, and you'll see where to make changes. I'm quite certain the mobiready tool can do something similar, I was just a little too impatient to look for it ;)

Hope this helps!