comment on journal entry: switching to Internet Explorer's box model

:

• Box modeling
  In some cases that makes sense, however I see the padding for a box model is not part of the content, so changing the padding will then change the width of the element not the content. To each thier own. [Joe] [reply]
  your name:

  further description:

  please identify this object so I know you're not a spam bot:

  cherries
  lime
  orange
  

  pear
  apples
  melon
  

  
  
  
• contents vs element
  Joe: I see the padding for a box model is not part of the content, so changing the padding will then change the width of the element not the content
  
  So, if I understand you correctly, you prefer that the content is preserved in its "natural" width and height, and that the padding serves to change the width and height of the container.
  
  The problem I have is that I often want a container to take a specific width and height, which I specify with the css width and height attributes. If, using the W3C model, I want to tweak the space between the bounds of the container and the contents, I must change both the padding and defined width of the container, having to do sums in my head to work out the new width/height minus the padding change. [Chris Beach] [reply]
  your name:

  further description:

  please identify this object so I know you're not a spam bot:

  apples
  lime
  tomato
  

  strawberry
  orange
  banana
  

  
  
  

[view more replies on journal entry switching to internet explorer's box model]