Filter
Top Products
Nokia 9210 Communicator
WWW Browser Style Guide
14 (14)
Version 1.2
18/1/2001
ãNokia Mobile Phones
If you get an error note from the web browser which says that a secure connection could not be established, the most
common reasons are:
• The site only supports SSL version 2, which is a very old version of the SSL security protocol. An upgrade to SSL
version 3 capable server would be recommended.
• The site supports SSL, but is configured to do SGC (Server Gated Cryptography, also called ramp-up cryptography)
negotiation. This is a way in which some U.S.-origin browsers operated in the past. If the site presented a certain
type of certificate, the SSL connection was re-established with a stronger suite of cryptographic algorithms. The
reason for this was to allow certain sites, such as financial institutions, to use strong cryptography, and at the
same time restrict all other sites to weak cryptography. The Nokia 9210 Communicator natively supports strong
cryptography, and has no need or support for SGC. The site should be upgraded to use strong algorithms in all
connections.
• The site requires a client certificate. This is very rare, but may be a case on some mail servers. The Nokia 9210
Communicator does not support client certificates. The server should be configured not to require a client-side
certificate.
6.2.3 Some frames are too small
Some sites use frames that are using a fixed width or height. When rendered on a small screen, these frames eat up
the screen and leave only a small portion of the screen for the rest of the frames. The optimum solution is not to use
frames at all, but if that is not an option, the frames should be allowed to dynamically resized. Also, for clarity, there
should not be too many parallel frames or frames inside frames.
As an user, you may opt to use another frame display mode, for example a single frame with a list of frames, or you
can open the currently selected frame as a new page (effectively discarding all other frames).
6.2.4 A link or a form button does not work
The most common reason for this is the use of JavaScript in the link or the button. As the Nokia 9210 Communicator
web browser does not support JavaScript, these links and buttons should have normal URL targets and not JavaScript
function calls.
Also, if a form has no clickable submit button, it is not possible to submit the form.
6.2.5 Characters in submitted forms display incorrectly
The Nokia 9210 Communicator uses a 16-bit Unicode character set, whereas most form submissions are made using a
8-bit character set of the ISO 8859 family. Unicode is not used in form submissions by default because of
interoperability problems with most web services. This results in some of the characters not being sent correctly to the
web server. As an example, the Euro sign (€) is not included in ISO 8859-1, which is used when sending forms from an
English language communicator, and cannot therefore be included in a form submission.
What the service operator can do is to suggest that users use certain other characters in the place of missing ones (for
example, the ¤ character instead of €). As a move towards an international web, the service should also support
Unicode (most notably the UTF-8 encoding) so that future versions of web browsers can use Unicode to get rid of
character set problems completely.