luke.bace (66) [Avatar] Offline
#1
Please post all errata here. Thanks.
hettlage (34) [Avatar] Offline
#2
Re: Errors and Corrections
In the last sentence on page 93

"the user can pick one of the options using the cursor keys or time his own"

presumably should be

"the user can pick one of the options using the cursor keys or type his own"
hettlage (34) [Avatar] Offline
#3
Re: Errors and Corrections
In AJ's second comment on page 98

"then the UI is not implemented by the browser and you should provide our own"

should be

"then the UI is not implemented by the browser and you should provide your own"
nyITguy (2) [Avatar] Offline
#4
Re: Errors and Corrections
Page 5, first sentence of first paragraph in section 1.1:

"In this section you'll learn just enough about HTML and CSS are to understand
the rest of this chapter."

Should be:

"In this section you'll learn just enough about HTML and CSS to understand
the rest of this chapter."

[Note: this comment refers to the PDF version of the introduction made available on the title's manning.com page.]
nyITguy (2) [Avatar] Offline
#5
Re: Errors and Corrections
Page 7, in description of CSS rules components:

"...a comma separated set of declarations inside curly brackets..."

Declarations are separated by semicolons.

http://www.hwg.org/resources/faqs/cssFAQ.html#mult_decl

[Note: this comment refers to the PDF version of the introduction made available on the title's manning.com page.]
josephmelnick (3) [Avatar] Offline
#6
Re: Errors and Corrections
Page 16:
"often find the the unambiguous format hard to digest"
should be
"often find the unambiguous format hard to digest"
josephmelnick (3) [Avatar] Offline
#7
Re: Errors and Corrections
Page 21:
but also more complex UI elements such as tree views,
dijit widget and dijit widget.

should be:
but also more complex UI elements such as tree views
and dijit widget.
josephmelnick (3) [Avatar] Offline
#8
Re: Errors and Corrections
Page 54:
submitting the form – possibly the the allowed values for a later field in the

Should be:
submitting the form – possibly the allowed values for a later field in the
bdpeterson (3) [Avatar] Offline
#9
Re: Errors and Corrections
Page 21, Section 1.3.2 of version 9 contains the following typo:
The idea behind them is that there is data is not directly relevant to the user but which does...

However it should read:
The idea behind them is that there is data [that] is not directly relevant to the user but which does...
bdpeterson (3) [Avatar] Offline
#10
Re: Errors and Corrections
Page 22 in section 1.3.2 under the comic:
Microdata uses three global attributes: item, itemtype and itemprop.

Item should be item should be itemscope.
bdpeterson (3) [Avatar] Offline
#11
Re: Errors and Corrections
Section 2.2 of v.9:
page 34 reads:
This example will increment of decrement in steps of 2:

Should read:
This example will increment [or] decrement in steps of 2:
jfs.world (83) [Avatar] Offline
#12
Re: Errors and Corrections
In the latest version of the MEAP, why does the width of the section and aside change from 54% / 25% to 70% / 30%? See book page 264, vs book page 265. (This is section 8.2.1 - "Mixing different length units with calc")
araigon (4) [Avatar] Offline
#13
Re: Errors and Corrections
pg 21: in response to the the generally -> in response to the generally
pg 63: if the the type -> if the type
pg 101: so the the results -> so the results
pg 123: the the CSS will 'win' -> the CSS will 'win'
pg 173: must be remove -> must be removed
pg 285: so that the the whole -> so that the whole
pg 347: according the the border -> acording to the border?
pg 382: Here's what the the three -> Here's what the three
bwolfe (8) [Avatar] Offline
#14
Re: Errors and Corrections
In section 2.1 consider changing "three ways of selecting from a predefined list of options" to "four ways of selecting from a predefined list of options" since the select method is shown w/and w/o the size= drop down / list box style.

Or consider grouping the select samples differently.

Brian W.
bwolfe (8) [Avatar] Offline
#15
Re: Errors and Corrections
In section 1.1 the HTML5 Elements diagram appears to have redundant examples in the bubbles. For example

1) In Header - Header appears twice
2) In Nav - Nav appears twice
3) In Footer - Footer appears twice

Brian W.
bwolfe (8) [Avatar] Offline
#16
Re: Errors and Corrections
In section 1.5 the Element / Content Model Category list is very hard to follow because the category headings wrap within words and because the rows and columns are not alternating white / gray background colors. It's hard to visually line stuff up while viewing the PDF.

Brian W.
bwolfe (8) [Avatar] Offline
#17
Re: Errors and Corrections
In section 2.2 "Browser support quick check" remember to re-check browser support before the final release.

Also suggest making sure the "Browser support quick check" table fits together on the same page.

Brian W.
bwolfe (8) [Avatar] Offline
#18
Re: Errors and Corrections
I section 2.3.3 change

"... based on whether they are current valid or invalid."

to

"... based on whether they are currently valid or invalid."

or

"... based on whether they are valid or invalid."

Brian W.
bwolfe (8) [Avatar] Offline
#19
Re: Errors and Corrections
In section 2.4 suggest making sure the "Emails and URLs" table fits together on the same page.

Brian W.
bwolfe (8) [Avatar] Offline
#20
Re: Errors and Corrections
In section 2.8.2 strike the 2nd "the" in the following:

"... possibly the the allowed values for a later
field in the form depend upon the user already having entered a valid
email address, or perhaps the input isn't part of a form at all."

Brian W.
bwolfe (8) [Avatar] Offline
#21
Re: Errors and Corrections
In section 2.8.3 the code example

<input type="range" name="two" onchange="exoutput1.value = one.valueAsNumber + two.valueAsNumber">

should be

<input type="range" name="two" onchange="out.value = one.valueAsNumber + two.valueAsNumber">

Brian W.
gregcharles (2) [Avatar] Offline
#22
Re: Errors and Corrections
In chapter 3, page 114, there is a chart showing browser support for canvas and SVG. It lists the IE versions 12 and 14, but I think it means 8 and 9, or maybe 9 and 10. The SVG scores also seems reversed for IE and Chrome based on the cited reference at coderead.com.

Chapter 2 also has a browser support chart listing IE 12 and 14.
gregcharles (2) [Avatar] Offline
#23
Re: Errors and Corrections
Ah, I see. It's the IE icon on the Chrome column and vice versa. It's corrected in subsequent tables.
robert.crowther (59) [Avatar] Offline
#24
Re: Errors and Corrections

Thanks Greg. It looks like we made the same mistake in chapter 2 as well but got it right from chapter 5 onwards. The order looks to be correct in all cases (alphabetical: Chrome, Firefox, IE, Opera, Safari) but the Chrome and IE icons are swapped.



Rob

pflutzke59 (1) [Avatar] Offline
#25
Re: Errors and Corrections
In appendix D, pages 503 and 504 I found a curious bit of code to determine if a number is odd or even. Page 503 shows this code:
if (x % 2 == 0) { console.log ('Even'); } else ....

My attempts using this code failed. Should it not be written as:
if (x/2==0) ?

A similar test appears on page 504. I apologize if the error is mine in not recognizing the use of %. I've never seen it used in this context.
bluehrmann (1) [Avatar] Offline
#26
Re: Errors and Corrections
On page 54, there is an error in the example for "output" element.

The code:

<fieldset>
<legend>Output example</legend>
<label for="one">Number: </label>
<input type="number" name="one">
<label for="two">Range: </label>
<input type="range" name="two" min="0" max="10">
</fieldset>

should be changed to:

<fieldset>
<legend>Output example</legend>
<label for="one">Number: </label>
<input type="number" id="one">
<label for="two">Range: </label>
<input type="range" id="two" min="0" max="10">
</fieldset>
robert.crowther (59) [Avatar] Offline
#27
Re: Errors and Corrections
% is the modulus (or remainder) operator: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Arithmetic_Operators

What browser were you having problems with?