.week 6 { day: 2; }
So much CSS, so little that makes any sense
Today we did nothing but CSS (well, and some HTML, but otherwise all CSS). No JS. No Rails. No lovely, sweet Ruby. Just evil, disgusting CSS.
Ok, so it wasn't THAT bad. But CSS does some really weird shit sometimes. One of the problems my partner and I had (in fact, almost every one of the problems we had today) was related to CSS's position property. While attempting to adjust the layering of two elements, we learned that the z-index property is ignored when an element's position is set to static. We also learned that every element's default position is static. A little later, we discovered that setting an element's position to relative does not, as one might expect, place the daughter element relative to any points of the parent's box model, but only adjusts the daughter element relative to where it would be if it were set to static. And finally, absolute position completely removes an element from the flow of the page and so does not factor into the resizing of its parent container(s). Yet, as we expected of relative, its position is calcualted relative to its parent. Knowing how relative positioning behaves, this one felt slightly more intuitive, but we still had to learn it the hard way.
It was a long day full of trial and error, but by the end, we at least knew we had mastered the position property. We did some fun stuff with border-radiuses as well. And we go to play with pictures of cats in the process. So it wasn't all bad.