Errata

jQuery Mobile

Errata for jQuery Mobile

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed, PDF Page 2
Example 1-1

http://code.jquery.com doesn't support version 1.0a4.1 any more.

Egon  Jul 11, 2011 
Printed, PDF, Other Digital Version Page 2
Example 1-1. Basic HTML 5

The author doesn't list the following statement:


<meta name="viewport" content="width=device-width,
initial-scale=1, minimum-scale=1, maximum-scale=1">

which is required to properly render the content on a mobile device.

Chuck McKnight  Oct 21, 2011 
Printed, PDF Page 3
Example 1-2 and 1-3

Neither example 1-2 nor 1-3 works - nothing is shown in the browser

Egon  Jul 11, 2011 
Printed, PDF Page 6
Below Figure 1-3

The text says "will automatically provide a back button in the header", but there is no back button.

Egon  Jul 11, 2011 
Printed Page 6
Below Figure 1-3

You are writing that jQuery Mobile automattcaly adds a back button. If you look at the jQuery mobile blog post in may, the back button is now off by default: jquerymobile.com/blog/2011/05/20/jquery-mobile-team-update-%E2%80%93-week-of-may-16th/

Anonymous  Oct 24, 2011 
Printed, PDF Page 13
Example 2-2

Also not working.
Maybe jQuery Mobile just isn't ready yet?

I don't want to waste more time :-(

Egon  Jul 11, 2011 
PDF Page 22
"Transitions" section, list of transitions

The description of the "slideup" page transition seems to imply that the current page slides up, revealing the next page below. In fact, the *next* page slides up from the bottom of the screen covering the current page. Essentially, "slideup" behaves like "slidedown" but with the next page arriving from the bottom rather than the top of the screen.

JamesPreston  Jul 13, 2011 
48
3.4.2. Button Icons Figure 3-19. Button icons

Button Icons...

Home...
Configure...
French!

"Search" would be appropriate.

Makiko Nomura  Jul 21, 2012 
Printed Page 56
Example 3-22

On page 55 you write "[...] apply the data-native-menu=false attribute to the select element, as shown in Example 3-22[...]" but I can't find the attribute data-native-menu in Example 3-22.

Anonymous  Oct 24, 2011 
PDF Page 61
2nd paragraph

The second sentence, "The containing div is given a class ui-grid class" does not make sense. Perhaps the first "class" should be removed?

JamesPreston  Jul 17, 2011 
PDF Page 85
CSS Selectors, 1st paragraph

The first sentence of the CSS Selectors section starts "jQuery Mobile will attach various CSS classes to the HTML element". This is a little ambiguous as it looks like "HTML element" could be any HTML element whereas it really refers to the <html> element at the document's root. Would "HTML" be better written in lower-case using a constant width font as the other element names in the book are?

This same problem occurs a number of other times in the same section (e.g. in the 2nd paragraph of CSS Selectors on p85).

JamesPreston  Jul 17, 2011 
PDF Page 89
List of options for configuring jQuery Mobile

In the latest version of jQuery Mobile (1.0b1), the "defaultTransition" configuration option has been renamed to "defaultPageTransition".

JamesPreston  Jul 13, 2011 
PDF Page 91
Last paragraph

On Page 91, the following text describes how jqmData() can be used to select all elements with a data-jqm-role="header" attribute, but it is actually selecting all elements with data-jqm-role="page" attribute:

$(":jqmData(role='page')") will select all of the elements in your application with the data-jqm-role="header" attribute.

Brad Browne  Dec 22, 2011