I'm looking at the dock skin CSS files, and they all set the padding for the dock zone to 4px 0 0 4px. Next, they set padding-right to 4px in a way that is apparently (according to the comments) hidden from IE6.
BUT, if you look at the dock.css file that appears in the install folder under skins, the last line is:
.raddockzone
{
padding: 4px !important;
}
Doesn't this force the padding for the entire dock zone to 4px regardless of what you put in the skin's CSS file? (I'm assuming, of course, that you're not overriding the setting via a selector for #dockzoneid.)
I've tested this by altering these settings in my skin's CSS file and don't see any affect, though I know that things are a little complex in there, so I wanted to verify this.
I'm suspecting these were settings that were left over from earlier implementations, and that the setting of this to 4px was to fix something with scroll bars.
Can you confirm?
Thank you.
5 Answers, 1 is accepted
The reason for having set the 4 pixels padding in the dock zone we have explained in the other forum thread concerning the same issue. Regarding your question whether the zone's 4 pixels padding in the Dock.css file forces this padding regardless of what it is set in the skin's CSS file it depends on the order in which the skin files are loaded. You can modify a built-in skin or use a custom skin and if you load the skin file after the base Dock.css skin file your padding setting in the skin file will be applied.
The RadDock's embedded base stylesheet - Dock.css which currently contains the zone's padding setting is loaded from the Telerik.Web.UI dll. If you add your custom skin reference between the head tags of the page dock's embedded base stylesheet will be loaded after your custom skin css file and it will override your setting. The easiest way to resolve the problem is to add the custom skin reference after the RadDock control (inside the body of the page). For your convenience I have attached a sample project which demonstrates how to achieve the explained above.
Sincerely yours,
Sophy
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Rank 1
Thank you for the information, and for the code sample. :)
I recently participated in that other thread, which is why I assumed there was a need for the 4 pixel padding. I didn't realize I was referring to the exact same code, though. (Oops!)
I was, however, more questioning the padding settings in your skin CSS files when that setting is forced to 4px in the base dock CSS file. It appeared that the padding settings in the skin CSS files were ignored. If that is the case, wouldn't it make sense to just remove them?
I've been wanting, for a while, to really learn the ins and outs of your skins, so I'm actually building skins from the ground up, starting with an empty CSS file and testing each definition as I add it. Generally, I add a setting and set it to some exagerated value to see the effects.
Thank you.
We agree that the padding setting to the RadDockZone in the base dock CSS file causes come inconveniences. We entered this issue in our requests list for further consideration and will do our best to fix this shortcoming for one of the next updates of the control.
If you have any other questions, do contact us again.
Best regards,
Sophy
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Rank 1
Thank you.
I was thinking that you should remove the settings in the skin-specific CSS files that are ignored due to the important! settings. But, if you're going to potentially remove them, it would make sense not to remove them.
IMHO, I think you really need to have padding below each dock. When I wrote my code that dynamically creates docks, I overrode the style to have the bottom padding. Now that I'm working with the skin files, I couldn't figure out how I got that padding!
Again, thank you.
Thank you for your feedback. We highly appreciate it.
I understand your point. We do not think to remove the padding setting at all. As I mentioned in my previous reply we will further consider the zone padding issue and provide the best possible resolution to the inconvenience the current setting causes.
Sincerely yours,
Sophy
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.