Cross Browsers CSS Debugging
06/06/수

노는 날이네요? 모하고들 노세요?

오늘은 @Tw Shim횽아가 투척해주신 읽을 거리로 만들어 봤습니다.

http://www.stubbornella.org/content/2012/05/02/cross-browser-debugging-css/
Do you work a lot with CSS?
Display
1. I think of CSS like a choose your own adventure.
2. When you have made certain choices, others become obvious.
3. For example, you need to first choose your display type block, inline, inline-block, table.
4. When you have chosen that, you are left with a tool-box of appropriate tools to use to alter the display.

5. For example,
6. Block level elements should be used with margins, paddings, height and width. Line-height isn’t appropriate.
7. Inline elements have line-height, vertical align, and can also be whitespace sensitive.
8. Margins, paddings, heights, and widths aren’t appropriate.
9. Tables have vertical and horizontal alignment and can sometimes behave bizarrely if you have one element of a table without the others (e.g. a table-row with no table-cell). 10. Margins are inappropriate for table-rows and table-cells.
11. Padding is inappropriate for tables and table rows.
12. If you stick to the tool box that naturally goes with your display type, you will have far fewer bugs and cross-browser differences.
1. 1번과 2번의 의미가 와닿으시나요? 예를 들어서 설명해 보세요.
Your answer
2. 위 문장 중에서, 설명을 듣고 싶은 문장이 있으면 골라주세요~
3. 나의 디버깅 프로세스를 곰곰히 떠올린 후 써주세요.
영어로 쓰실 거죠? CSS가 아니어도 괜찮습니다.
Your answer
수고하셨습니다. ^^
오늘은 좀 짧죠?
오늘도 짧고 굵게 공부한 나에게, 어떤 선물 주시겠어욤?
밥, 드라마 보기
Your answer
짧은 피드백 부탁해요~
1
2
3
쉬우셨나요? (어려울수록3)
내일도 풀고 싶으세요? (풀고 싶을수록 3)
Submit
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google.