Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...XHTML 1.0 Strict validationXHTML 1.0 Strict validation
Previous
 
Next
New Post
5/30/2007 8:01 AM
 

The 4.5.2 version very nearly validates out of the box.

Just tried a test install, installed my own menu component and a div based skin. created a test page with a html module.

It validates correctly if you amend the default.aspx line:

 <body id="Body" runat="server" bottommargin="0" leftmargin="0" topmargin="0" rightmargin="0" marginwidth="0" marginheight="0">

to be

 <body id="Body" runat="server">

Obviously this is the simplest possible case, but it's a great step forward!

 

 
New Post
5/30/2007 8:24 AM
 

FYI: I've a few other xhml/accesibility fixes for the next version that will remove that issue also. At present you can workaround it by modifying the default.aspx as Isomies suggests or else by adding some server code into your ascx to remove the unwanted attributes from the body tag e.g.

Body.Attributes.Remove("bottommargin")

Body.Attributes.Remove("leftmargin")

...etc.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/30/2007 9:54 AM
 

Interested to hear about the next version fixes - are they in Gemini?

Just updated http://www.northmarket.se to 4.5.2 - had to make a couple of changes, adding type=""text/javascript" to the various javascript blocks that are inserted in ClientAPI.vb and a change to the ClientAPICaps.config from

<functionality nm="SingleCharDelimiters" desc="Supports single character delimiters (i.e. Char(18))">
  <supports>
    <browser nm="*" />
  </supports>
  <excludes>
    <browser contains="Mac_PowerPC)" />
  </excludes>
</functionality>

To:

<functionality nm="SingleCharDelimiters" desc="Supports single character delimiters (i.e. Char(18))">
  <supports />
  <excludes>
    <browser contains="*" />
  </excludes>
</functionality>

And it's all validating again. Nice.

 
New Post
5/30/2007 10:05 AM
 

Cathal,
thanks for your updates.

It will be fixed also the issue stated by Nokiko "....The core modules I do use i have to modify because the standard modules inject a  span class="normal tag around the module content. This is not allowed because a span is an inline element and all module content des have block level elments in them rendering the code immediately invalid..." ?

For me this "span" tag wrapper injected by the code that does not allow divs inside is the most important and top priority to be fixed by the dnn core team for XHTML validation.

bye
Luca

 
New Post
5/30/2007 12:25 PM
 

For me this "span" tag wrapper injected by the code that does not allow divs inside is the most important and top priority to be fixed by the dnn core team for XHTML validation.

That has already been addressed. See my posts above.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...XHTML 1.0 Strict validationXHTML 1.0 Strict validation


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out