Patrick Malley

The only way to succeed is to create good documentation to get people to work quite fast. And with good Moodle documentation nobody needs to reed the original documentation Matt created and nobody will be confused any more. Right?

Good point. The naming scheme should define the areas. Yours works fine. I was looking for more of an explanation than a convincing argument. Thanks!

Urs, can you explain how your naming scheme improves things any better? Why not use Matt's IDs exactly as they are so there is no confusion to developers who want to use it?

A solution has been filed:

MDL-22108

The scrollbars are being created inside the sideblock stylesheets where they appear.

Specifically:

- /moodle/blocks/settings_navigation_tree/styles.css
- /moodle/blocks/global_navigation_tree/styles.css

These two blocks have nearly identical CSS.

To fix, this:

.block_settings_navigation_tree .block_tree {margin:5px;padding-left:0px;overflow-x:auto;overflow-y:visible;}

becomes:

.block_settings_navigation_tree .block_tree {margin:5px;padding-left:0px;overflow:visible;}

And, this:

.block_settings_navigation_tree .block_tree .tree_item {white-space:nowrap;margin:2px 0px;padding-left: 16px;margin:3px 0px;white-space:nowrap;text-align:left;}

becomes:

.block_settings_navigation_tree .block_tree .tree_item {margin:2px 0px;padding-left: 16px;margin:3px 0px;text-align:left;}

Then, this gets deleted:

.ie7 .block_settings_navigation_tree .block_tree {overflow-x:scroll;}

This removes the scrollbar and wraps lines that are too long.

Thanks Mary. This is a big help. But, have you tried to implement this? There is a lot of additional CSS in pagelayout.css that I don't quite understand. If you've gotten it to work, please share. I'd be grateful.