Here it is.

Fore example Color works in the .no_header_contentpane style, but all font stuff does not since the text gets encepsulated in <p> tags

<div>
  <div id="no_header_toppane">
    <dnn:ACTIONS runat="server" id="dnnACTIONS" ProviderName="DNNMenuNavigationProvider" ExpandDepth="1" PopulateNodesFromClient="True" />
    <dnn:ICON runat="server" id="dnnICON" />
    <dnn:ACTIONBUTTON1 runat="server" id="dnnACTIONBUTTON1" CommandName="ModuleHelp.Action" DisplayIcon="True" DisplayLink="False" />
  </div>
  <div id="no_header_contentpane">
    <div id="ContentPane" runat="server" class="no_header_contentpane" />
  </div> 
  <div id="no_header_bottompane">
    <dnn:ACTIONBUTTON2 runat="server" id="dnnACTIONBUTTON2" CommandName="AddContent.Action" DisplayIcon="True" DisplayLink="True" />
    <dnn:ACTIONBUTTON3 runat="server" id="dnnACTIONBUTTON3" CommandName="SyndicateModule.Action" DisplayIcon="True" DisplayLink="False" />
    <dnn:ACTIONBUTTON4 runat="server" id="dnnACTIONBUTTON4" CommandName="ModuleSettings.Action" DisplayIcon="True" DisplayLink="False" />
  </div>
</div>



{}#no_header_contentpane
{}

.no_header_contentpane

#no_header_toppane

I have no other style with that name.

The funny thing is that the color stuff works...

Allen,

Be careful using any IDs in containers.  Containers can occur more than once on a page which would make the ids invalid.  Identification versus classification.  For instance, if you were a container an ID would be something like "Allen" and a class would be "male" or "finger".  Second, DNN rewrites many of the IDs for its programming needs changing the CSS environment.  It is much safer in general to style DNN pages using classes.

To give further advice, we would have to see the page so we can see what inheritance issue you are dealing with.