OYEWAP.COM

 
  Do all WAP devices (browsers) comply with WML specifications?

No. WAP device developers will constanty try to push the envelope on the specifications as WAP takes off. This makes life "interesting" for developers, but it also ensures the rapid growth of the technology.
 
Below is the first attempts at creating a matrix that will first of all help you develop applications that work well on all devices, but also help you identify and solve problems related to browser differences. The matrix will most certainly grow to galactic proportions.
 
AnyWhereYouGo.com also has a detailed list here which you will find very useful

Nokia 7110 Ericsson R320 Ericsson R380 UP.Browser
Max card size 1397 bytes 3000 bytes 3800 bytes 1492 bytes
Max image size 1397 bytes 3000 bytes? 3800 bytes? 1492 bytes?
Rows in display 4 plus title 5 7 Device dependent
Cols in display 19 14 Unknown Device dependent
Horizontal pixels in display 95 101 304 Device dependent
Vertical pixels in display 45 52 98 Device dependent
Pixel display ratio 1:1.25 Unknown 1:1.23 Device dependent
Text style None Small, Bold, Emphasis, Strong Small, Big, Bold, Italic, Emphasis, Strong Small, Big, Bold
Text alignment None. Forced left. Left, Center, Right Left, Center, Right. Idented paragraphs Unknown
Image alignment Forced center Unknown Unknown Unknown
Tables support None Maximum 5x5 cells Unknown Unknown
Touch screen No No Yes No
Icon buttons No No Yes Unknown
Calling numbers within WML "Use number" function Supported through WTAI Supported through WTAI Supported in v.3.1 and higher
Input elements Alone on row Where placed Where placed Uknown
Input formatting Only A, a, N, X, x, M, m and * Unknown Unknown Uknown
Image links No Yes Yes Unknown
Links formatting Alone on row Where placed Where placed Unknown
Deck load sequence Text, then images, then optional timer start Text, then optional timer start, then images. Note that timer may run out before card is shown as a result Unknown
HTTP Redirect Supported Supported Supported Supported