The content in the "main page content" block already has its own wrapping divs, whether its the node or panel or View, whatever. Adding a block wrapper around it is redundant.
The content region is already placed in a div#content so that can be placed in the same column as the title, help, tabs, etc. So adding a region wrapper around the content is also redundant.
We can easily get rid of these wrappers by creating a region--bare.tpl.php and a block--bare.tpl.php that have been stripped of their wrapping divs and then adding a template suggestion for the main page content block and content region.
Comments
Comment #1
JohnAlbinFixed. http://drupalcode.org/project/zen.git/commit/786931f
Comment #3
OnkelTem CreditAttribution: OnkelTem commentedBut removing the block wrapper makes it impossible to address Any content or how it is supposed to stylize #content insides?
"title, help, tabs" as you said - have their names and addressable. Now after removing the wrapper content becomes the only anonymous entity.
In short, this breaks everything which relies on existence of ".region-content". For example, the only place where a custom contextual links could be attached is .region-content. Now after this is removed, things like http://drupal.org/sandbox/onkeltem/1730244 have no chances to survive... in sake of this rationalization effort. I vote for not removing region-content.
Comment #4
OnkelTem CreditAttribution: OnkelTem commentedComment #5
OnkelTem CreditAttribution: OnkelTem commentedComment #6
echoz CreditAttribution: echoz commentedDoesn't this give you what you need?
Comment #7
OnkelTem CreditAttribution: OnkelTem commentedI don't mean that overriding has any difficulties, just wonder why this is by default.
Comment #8
echoz CreditAttribution: echoz commentedMy understanding of this is to lighten up the markup.
Comment #9
OnkelTem CreditAttribution: OnkelTem commentedThen why not to lighten it more and remove half of standard Drupal HTML? I still don't get how to address content without .region-content.