|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
February 16th, 2007, 02:52 PM
|
|||
|
|||
How strict are WAP 2.0 browsers?
Will a WAP 2.0 browser only accept valid XHTML MP and WML?
If the WAP 2.0 device goes through a gateway, will the proxy attempt to format/transcode a regular html page (like WAP 1.x gateways do)? Will the device itself try to format/transcode a regular html page to XHTML MP if there isn't a gateway? I'm just curious of how much tag soup and kinds of headers it can handle, if any. Last edited by bug_m3_n0t : February 16th, 2007 at 03:32 PM.
|
|
#2
February 23rd, 2007, 12:46 AM
|
||||
|
||||
|
I can't really comment on the gateway questions but for the valid XHTML / WML:
these are both derivatives of XML, therefore they need to be coded correctly, eg tags closed and the XML is well-formed. As XHTML should be sent to the browser as application/xhtml+xml or application/vnd.wap.xhtml+xml - these will break if not well formed. I assume that you are trying to do something more than just server web pages to mobile devices? Many phones, as you well know, can handle regular HTML too....
__________________
Cheers, Jamie # mdb4u | mobile movie database] | Please help to test and promote # skiFFie | Home of the 'accessibility module' for Drupal # Jamie Burns [me] Accessibility Module [drupal] # guidelines | search | wap resources | not getting help | fold to cure __________________ Let the might of your compassion arise to bring a quick end to the flowing stream of the blood and tears ..... Please hear my anguished words of truth.  __________________
|
|
#3
February 26th, 2007, 02:25 PM
|
|||
|
|||
|
I'm trying to put a summary together on the state of mobile web. Ridiculously, I don't even have a web enabled phone so I'm just basing everything on reports from around the web.
So, to recap – WAP 2 browsers demand valid code and HTML browsers don't? If unvalid: Will the WAP 2 browser just throw an error or will it attempt to render what it thinks it should?
|
|
#4
February 26th, 2007, 07:22 PM
|
||||
|
||||
|
Most phones require that the content is sent with the correct header info (content type).
The same could be said for Firefox for example. You can send XHTML as application/xhtml+xml. You can see a few pages out on the web that just don't display cause their content is mal-formed. XML Parsing Error: mismatched tag. Expected: For a comparison chart for XHTML profiles, see this. Maybe helpful at some point.
|
|
| Viewing: Dev Shed Forums > Programming Languages - More > Mobile Programming > How strict are WAP 2.0 browsers? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
