July 2006 Archives
- Archive navigation
- April 2006
- Home
- May 2007
XMLHttpRequest Object methods
| Method/Property | Description |
|---|---|
| abort() | Stops the current request. |
| getAllResponseHeaders() | Returns the response headers as a string. |
| getResponseHeader("headerLabel") | Returns a single response header as a string. |
| open("method", "URL"[, asyncFlag[, "userName"[, "password"]]]) | Initializes the request parameters. |
| send(content) | Performs the HTTP request. |
| setRequestHeader("label", "value") | Sets a label/value pair to the request header. |
| onreadystatechange | Used to set the callback function that handles request state changes. |
| readyState | Returns the status of the request: |
| 0 = uninitialised | |
| 1 = loading | |
| 2 = loaded | |
| 3 = interactive | |
| 4 = complete | |
| responseText | Returns the server response as a string. |
| responseXML | Returns the server response as an XML document. |
| Status | Returns the status code of the request. |
| statusText | Returns the status message of the request. |
- Filed under:
- Web design
- AJAX
- JavaScript
Mobile Web Guidelines
With input from big players such as Google, Microsoft, Nokia, AOL, AT&T, Ericsson, GoDaddy, and Vodafone the W3C have defined a set of basic guidelines for developing mobile Web content.
Mobile Web Best Practices 1.0, consists of instructions on how to avoid technical issues when viewing web content from mobile devices.
The guidelines also focus on how to prevent known problems such as pop-up windows, horizontal page scrolling and more. It is seen that these guides will aid content authors, web developers and web designers when planing to create websites that will also be available via mobile devices.
There is also a Wiki dedicated to the Mobile Web Best Practices, enabling people to actively respond and add valuable input.
Mobile Web Best Practices Wiki