HTML5 support

Well... HTML5 is quite a rich and big monster. So, what you mean with "support" here?

The problem I'm currently having trying to get the editor to handle HTML 5 content is that it wants to wrap unknown tags with paragraph tags. If there's a setting that will prevent this, I can't seem to find it.

Otherwise, if you include, at a bare minimum, an HTML 5 CSS reset to provide a few default styles, the editor seems capable of displaying HTML 5 content.

- jason

I wanted to ping this thread with an example of the problems I have when using HTML5 with the CKEditor.

If I use code like this:

<section>
   <header>
      <hgroup>
         <h1>
            Section Heading
         </h1>
         <h2>
            Section Subheading
         </h2>
      </hgroup>
   </header>

   <article>
      <h1>
         Article 1 Heading
      </h1>

      <p>
         Article 1 content.
      </p>
   </article>

   <article>
      <h1>
         Article 2 Heading
      </h1>

      <p>
         Article 2 content.
      </p>
   </article>
</section>

My code is transformed through the WYSIWYG into:

<p>
   <section>
      <header>
         <hgroup></hgroup>
      </header>
   </section>
</p>

<h1>
   Section Heading
</h1>

<h2>
   Section Subheading
</h2>

<p>
   <article></article>
</p>
<h1>
   Article 1 Heading
</h1>
<p>
   Article 1 content.
</p>

<p>
   <article></article>
</p>
<h1>
   Article 2 Heading
</h1>
<p>
   Article 2 content.
</p>

https://svn.fckeditor.net/FCKdtd2js/trunk/

alfonsoml,

Thanks for your assistance. I wrote my own html5.dtd, but I could not use FCKdtd2js. I receive the following error:

>java -jar FCKdtd2js.jar dtd\html401-strict.dtd
At line 81, column 8: Expected GT instead of NMTOKEN(--)
com.wutka.dtd.DTDParseException: At line 81, column 8: Expected GT instead of NMTOKEN(--)
        at com.wutka.dtd.DTDParser.expect(DTDParser.java:311)
        at com.wutka.dtd.DTDParser.parseEntityDef(DTDParser.java:916)
        at com.wutka.dtd.DTDParser.parseEntity(DTDParser.java:818)
        at com.wutka.dtd.DTDParser.parseTopLevelElement(DTDParser.java:262)
        at com.wutka.dtd.DTDParser.parse(DTDParser.java:121)
        at com.wutka.dtd.DTDParser.parse(DTDParser.java:103)
        at net.fckeditor.devutil.dtd.WutkaDTDParser.parseXmlDefinition(WutkaDTDParser.java:30)
        at net.fckeditor.devutil.dtd.DTDJsGenerator.run(DTDJsGenerator.java:137)
        at net.fckeditor.devutil.dtd.DTDJsGenerator.main(DTDJsGenerator.java:95)

Notice in this example that I'm actually trying to use the tool with one of the existing, included DTDs. I tried absolute paths and everything. Am I doing something wrong?

Sorry, I've never used it, so I can't tell what might be wrong.

Anyway, you must realize the the dtd.js file that it's being used has been manually tuned afterward to reflect extra data so it might be easier try to adjust that file (I don't know, I haven't tried it)

alfonsoml

http://dev.fckeditor.net/ticket/4990

CKEditor working with HTML5: http://sandbox.thewikies.com/ck-html5/

borked

modified ckeditor.jshttp://sandbox.thewikies.com/ck-html5/*mostly properly; some things, like anchor links around block elements, are still not workingunmodified ckeditor.jshttp://sandbox.thewikies.com/ck-html5/sans.html

http://sandbox.thewikies.com/html5-ckeditor/

jonathantneal wrote:I've moved the demo to http://sandbox.thewikies.com/html5-ckeditor/

We'll be upgrading to CKEditor 3 in Liferay 6, but we're gonna go ahead and add in the HTML5 support ourselves, since CKEditor doesn't seem interested in updating it within theirs.

http://sandbox.thewikies.com/html5-ckeditor/dtd.js





http://dev.fckeditor.net/ticket/4556

Can't this be integrated into CKEditor future releases somehow?

matti wrote:Can't this be integrated into CKEditor future releases somehow?

We're integrating my patch into Liferay v6.0. I don't know why CKEditor did not get this into v3.2.

Does HTML5 have a priority with you folks?

http://dev.fckeditor.net/ticket/4556

I'm not quite sure why you say the CKeditor project isn't interested in html5... Did they close your ticket INVALID or something?

I have absolutely no idea. It's really confusing me. We switched to the YUI3 one, but I'd still love to see this, just because I've invested so much time bugging them and even trying to contribute.