Polycom, Inc. 84
Troubleshooting 7:The browsers that best match Polycom phone browsers are Chrome or Safari, as they are built on WebKit
as well. You can use Chrome or Safari to test rendering issues on the computer before testing them on
the phone’s browser.
When debugging Web pages, the Inspect Element in the phone simulator and in Chrome is very helpful in
finding coding issues. Also, Firebug is a useful Firefox add-on that can be used to debug Web pages.
To debug Web pages:
1 Use Firebug (in Firefox) or Inspect (in Chrome or the phone simulator) to check for JavaScript
errors.
2 Use Firebug or Inspect to check that all asynchronous requests are working properly.
3 Determine if there are server errors.
If there are server errors, use the generated error messages Apache logs to figure out the error.
4 Repeat this process until there are no errors.
Polycom has an active Developer Community Forum where you can find more sample code as well as
answers to many common developer questions. You can also post questions to Polycom support experts
and other developers.
This chapter also presents problems, likely causes, and corrective actions. Problems are organized into
the following categories:
Understanding Microbrowser Application Errors
Understanding Microbrowser Application Errors
The following table describes possible solutions to microbrowser application errors.
Table 69: Troubleshooting Microbrowser Application Errors
Improperly formatted tables can cause error ‘XML Error (17,75) mismatched tag’.
Solution: Correct the improperly formatted table.