Is it fair to assume that testing my code on a Retina MacBook Pro is sufficient? That is, I assume the resolution on my laptop competes size wise with most standard desktops, unless a person has a really big, hi-def monitor.
Can you please post the HTML elements that you feel are extraneous in a [ code ] box below?
Or maybe post my latest code in [ code ] tags and simply add a comment to make it easier for me to see where my code could be improved.
(The reason Microsoft created “Track Changes” in MS Word is that people need to see issues in the context of the original document, not a perfect rewrite where they can’t see where the issues were at, yeah know?!)
Also, not sure about your last comment. While my code uses pixels, I tested it pretty heavily and it looks great for a mockup.
Not sure where you feel it fails, but if you look above, @Coothead admitted there was an issue on his computer and not with my latest code…
It is not necessary to set checkoutItem dimensions because the script expands to fit inside pageBody and has the margin-bottom set to create a gap in the displayed checkoutItems/books. Also I set the default font-size to cascade.
itemAuthor, itemPublishedOn and itemUnitPrice are all spans that are redefined into blocks?
itemDescription is not required in my layout. I use a single plain div which follows the natural flow of the script and also wraps to make it responsive.
itemTitle is already a block which is over ridden into to a block?
using @media when it is not required
using flex and it fails to make the page responive
setting seven different font-sizes whereas I used two. The meta viewport should handle the font-sizes gracefully and not be over ridden
Take another look at post #30 where I described how I created the items in the block one at a time, starting at the top and working down. Hiding items which require modifying and applying background colours to highlight where the block starts and finishes. also making use of the native size and whether is is a block or a string.