https://forums.manning.com/forums/css-in-depth
JForum - http://www.jforum.netListing 1.5 on page 6 I flagged this to Manning Support and got this unhelpful reply (left/right-hand disconnected?)

[color=cyan]Hello Dick,

I am very sorry to hear this. Have you by chance posted this in our author online forum?

Ted
Manning Support[/color]
]]>https://forums.manning.com/posts/preList/39024/120994.pagehttps://forums.manning.com/posts/preList/39024/120994.page
GMTManning 'proof-readers' at it again. OK. Maybe it will look less weird when it's a diagram.

>>As for page 7, there is no error there.

'Following is a line of CSS' is not correct English. It should be 'The following is a line of CSS'.

I agree that the text isn't 'riddled with errors'. However, it only took me about three minutes to find these ones, so I suspect that there are dozens more. It depends on what you think is acceptable.

]]>https://forums.manning.com/posts/preList/42913/120910.pagehttps://forums.manning.com/posts/preList/42913/120910.page
GMTErrata in CSS in Depth Susan Harkins
Errata Editor
Manning Publications]]>https://forums.manning.com/posts/preList/42928/120875.pagehttps://forums.manning.com/posts/preList/42928/120875.page
GMTInstalling node-sass on Windowshttps://forums.manning.com/posts/preList/42429/120275.pagehttps://forums.manning.com/posts/preList/42429/120275.page
GMTManning 'proof-readers' strike again The MEAP you’re reading doesn’t reflect all the changes from final copy editing. Thanks for the heads up—I’ve double checked these passages in the final print edition, and they have all been corrected. They will be fixed in the final eBook/pBook you receive

The email which was sent out specifically said that the text had been proof-read, supposedly by an entire team of people.]]>https://forums.manning.com/posts/preList/42428/120274.pagehttps://forums.manning.com/posts/preList/42428/120274.page
GMTSource order of media queries Yes, this statement applies specifically to these two particular media queries and the code within. I go into media queries at much greater depth in chapter 8 on responsive design. I cover where to order media queries in general in that chapter.]]>https://forums.manning.com/posts/preList/42566/120270.pagehttps://forums.manning.com/posts/preList/42566/120270.page
GMTTypo in ch 3https://forums.manning.com/posts/preList/42332/119139.pagehttps://forums.manning.com/posts/preList/42332/119139.page
GMTRobert C. Martin referencehttps://forums.manning.com/posts/preList/41448/119075.pagehttps://forums.manning.com/posts/preList/41448/119075.page
GMTListing 7.6 .dropdown-menu {
display: none;
position: absolute;
left: 0;
[b]top: 2.1em;[/b]
min-width: 100%;
background-color: #eee;
}

Using top: 2.1em relays over the size of the dropdown label and the padding around it (.5em top and bottom).
Generally I think that using top: calc(100% + .1em) is a more solid approach as it allows to change the padding / font size freely]]>https://forums.manning.com/posts/preList/42351/118877.pagehttps://forums.manning.com/posts/preList/42351/118877.page
GMTWrong flexbox shorthand declarationhttps://forums.manning.com/posts/preList/41899/117904.pagehttps://forums.manning.com/posts/preList/41899/117904.page
GMTWhy padding, not margin for float based grid systemhttps://forums.manning.com/posts/preList/41871/117903.pagehttps://forums.manning.com/posts/preList/41871/117903.page
GMTCannot use varhttps://forums.manning.com/posts/preList/41977/117902.pagehttps://forums.manning.com/posts/preList/41977/117902.page
GMTMinimum sizing algorithm of flex itemshttps://forums.manning.com/posts/preList/41232/116351.pagehttps://forums.manning.com/posts/preList/41232/116351.page
GMTWhy use lobotomized owl to apply top margin and then remove it? Cheers]]>https://forums.manning.com/posts/preList/41141/115555.pagehttps://forums.manning.com/posts/preList/41141/115555.page
GMTContradiction on default values of flex-shrinkhttps://forums.manning.com/posts/preList/41142/115548.pagehttps://forums.manning.com/posts/preList/41142/115548.page
GMTDoes listing 4.19 need the .clearfix styles? [code]
.clearfix::before,
.clearfix::after {
display: table;
content: " ";
}
.clearfix::after {
clear: both;
}
[/code]

(looks the same without it AFAICT).

Also, the rows aren't of equal heights (because the text in them varies). Would it make sense to set a `min-height: 170px;` on `.media`? Or I guess using some em value but I forgot how to calculate those from the beginning chapter.

>>Speaking of which, Grid is one. It's not fleeting. It's here to stay, and its support by browsers will only grow (and well before 2027, by the by).

Let's hope that eventually it becomes usable in production: I will certainly use it when it is. For the next few years, though, we will have to wait for those users who don't upgrade their browsers to ditch their old computers and buy new ones and for companies whose intranets depend on a particular old version of IE to go bust. And also for Microsoft to a) adopt it and b) adopt it properly. Given Microsoft's track-record of breaking browser standards over the years, b) may be a long wait.

>> Any CSS publication worth its salt will cover this feature, because it is forward-thinking to do so.

I agree that it should be mentioned. However, not at the expense of technologies such as PostCSS or SASS which are core skills any CSS designer needs in 2017. Moreover, he should add much clearer 'health warnings' about Grid, Flexbox and other new technologies. Newbies might well not understand the risks of using them. If he added a chapter on PostCSS and referenced the relevant plug-ins throughout the text then the problem would be solved.

>>If your argument is that Grid should not be covered in this book because it won't be useful or well-supported, then I don't buy it, and we will simply have to agree to disagree.

Default value for svg CSS:
[quote]transform-origin: 0 0[/quote]]]>https://forums.manning.com/posts/preList/39638/110815.pagehttps://forums.manning.com/posts/preList/39638/110815.page
GMTMaybe we could add details about "flex-basis: 0%" into the book Good catch on the `flex-shrink: 1`. I'll update that.]]>https://forums.manning.com/posts/preList/39570/110760.pagehttps://forums.manning.com/posts/preList/39570/110760.page
GMTwhat is this "margin" in media body? Normally, this element would surround the floated image, taking up the full width of its parent. But since we established a new block formatting context (using `overflow: auto`), the element is shifted to the right, beside the floated image. The width of the element is then constrained by the edge of the parent. This orange highlights any area included in the natural width of the `modal-body`, but where its contents won't actually flow. You'll notice the width of this orange area exactly matches the width of the image.

This can be a little confusing, and I'm not entirely sure why DevTools displays the area like this.]]>https://forums.manning.com/posts/preList/39535/110759.pagehttps://forums.manning.com/posts/preList/39535/110759.page
GMTPlease help to explain what 'clearing' and 'catch' mean here? We fix this by using the `clear` property, listing 4.8.[/quote]

May I take it this way:
box 3 is going to the far left end on his own way or on the row it resides.
So "clear" means to clear everything out of his way which may block it.
"catch" means box 3 is stuck by box 1 which stops box 3 to get to the left end.

Sorry for being so inquiring in advance, I googled the word "catch on" and found two meanings of it:
1. To understand something
2. To become popular
which make me confused...]]>https://forums.manning.com/posts/preList/39526/110528.pagehttps://forums.manning.com/posts/preList/39526/110528.page
GMTWhy 2vw becomes 7.5px on iphone 6? Ahhh~ I get it. My fault, I didn't get the point clearly.
iPhone is not tablet at all.
Thank you for your response.
Nice work!]]>https://forums.manning.com/posts/preList/39478/110473.pagehttps://forums.manning.com/posts/preList/39478/110473.page
GMTCode Listings Repositoryhttps://forums.manning.com/posts/preList/38982/109332.pagehttps://forums.manning.com/posts/preList/38982/109332.page
GMTA notation for specificity The selectors from listing 1.7 are indicated as follows: