Hi Alex,

I agree that not changing the core files would be the best as this makes it challenging when upgrading your DNN versions as your changes can be overwritten.

I'm not really sure what the original reason for adding the normal class was, but I believe it is some legacy override approach from long ago. The class is added dynamically to each container on the server side. The best way to handle it would be to just add a new definition with the normal class. For example:

p, .normal p { font-size:13px;}

To be honest, it has been a challenge for skinning for quite some time.

---

 

Although there are modules (like the HTML module) that add Normal class (as Ralph stated for historic reasons), the class of the container is injected in the container.ascx and can thus be removed from the container.
Most containers add this class for downwards compatibility I guess.
If are creating a new container, you have to inject a contentpane control, by default this mostly looks like this:

 <div id="ContentPane" runat="server" class="Normal cContentpane"></div>

But, you can also use:

<div id="ContentPane" runat="server"></div>

And you willnot have the .Normal class

BTW, I guess the biggest problem is that default.css adds styling for the .Normal class.

---