Hey can you give me a specific example that's bothering you?
Re:CSS Diner
by JoshTriplett on Tuesday March 25, 2014 @02:12AM
(#7464179)
One example of how it should work: On puzzle 1, the expected solution is "plate", but * works fine; that's completely OK because puzzle 2 forces you to use a more specific selector.
On level 7, it's possible to ignore the intended lesson and use "plate .small, bento .small".
On level 10, surprisingly, it's not possible to ignore the intended lesson and write "apple, orange, bento, plate".
On level 11, .table * * works, though that does use the intended lesson.
That's in addition to the ones already mentioned in the sibling comment, which were the first ones I noticed.
I did several of them this way as well. At first I wasn't even reading the description to the right and just typing in selectors based on the instructions. So if I knew two comma separated selectors would work then that's what I typed in. Without going back over it to check, it's possible I entered selectors on a good number of them totally different than what was expected.
It would be interesting if the answers were tracked so we could eventually see what different developers were entering as selectors on each one.
Re:CSS Diner
by lifthrasiir on Tuesday March 25, 2014 @01:38AM
(#7464062)
Some examples: `plate>apple, plate>pickle` for 16, `apple, pickle` for 17, `bento:nth-child(2)` for 19, `plate:nth-child(2)>apple` for 22.
One notable issue: several puzzles need to have additional elements or classes added to prevent less sophisticated solutions from working. It's often possible to use a simpler selector than the one being taught in a particular puzzle.