I am already a happy FleXhtml user :-). But the lists I'm working with must be generated from flexwiki syntax, so I guess I'll have to live with this nesting problem for the time being...
> Well there is a solution, but not a fix. I guess I was anticipating your > question when I responded to another issue on the maillist last week. > Friday > I created a blog entry [1] which shows how to get the correct XHTML output > using a plugin I have created (and how to get complex item numbering). > The fix depends on how quickly a new parser arrives. Once we have that > then > we can look at redoing the output code to be fully XHTML compliant. The > project is about to start a discussion on what the next steps are now that > 2.0 has just been released. > > [1] > http://ods.dyndns.org/FlexWiki/default.aspx/OdsWiki/JohnDavidsonBlog.html > > John Davidson > > On Jan 15, 2008 10:15 AM, <[EMAIL PROTECTED]> wrote: > >> > The lost output is correct html (though deprecated). The requested >> output >> > is >> > required for XHTML compliance. FlexWiki outputs a number of HTML >> sequences >> > that are allowed in HTML, but do not meet XHTML requirements. >> > The upgrade to FlexWiki 2.0 corrected a number of similar items and >> tried >> > to >> > get as much output as possiblein XHTML compliant mode. This will be a >> > continuing effort (there is an open feature request for that) and is >> > partially dependent upon a new parser, as the current output formatter >> is >> > structurally difficult to modify without a full rewrite. >> >> Does this mean I shouldn't expect a solution soon? >> >> > I have checked that IE7 has the same incorrect output as both FireFox >> and >> > Safari. It does _not_ self-correct and renders the tags as output by >> > FlexWiki - that is in deprecated format. >> >> Unfortunately my target platforms are IE6 and Firefox... >> >> > John Davidson >> > >> > On Jan 15, 2008 6:36 AM, <[EMAIL PROTECTED]> wrote: >> > >> >> Hi all, >> >> >> >> I've got a bug report (feature request?) concerning nested lists. At >> the >> >> moment, the html flexwiki generates for something like this >> >> >> >> * list1item1 >> >> * list2item1 >> >> * list2item2 >> >> * list1item1 >> >> >> >> looks like this: >> >> >> >> <ul> >> >> <li>list1item1</li> >> >> <ul> >> >> <li>list2item1</li> >> >> <li>list2item2</li> >> >> </ul> >> >> <li>list1item2</li> >> >> </ul> >> >> >> >> Interestingly, while Firefox (tested version 2.x) creates its dom >> tree >> >> like above, Internet Explorer (tested version 6) ends up with a >> slightly >> >> different dom tree (from the same html!): >> >> >> >> <ul> >> >> <li>list1item1 >> >> <ul> >> >> <li>list2item1</li> >> >> <li>list2item2</li> >> >> </ul> >> >> </li> >> >> <li>list1item2</li> >> >> </ul> >> >> >> >> IE seems to internally "correct" the delivered html. Whouldn't it be >> >> better if FlexWiki generated nested lists like this "corrected" >> version >> >> in >> >> the first place? Because, at the moment we end up with different dom >> >> trees >> >> in different browsers, and as I have to do lots of javascript >> >> manipulations to nested lists generated by Flexwiki, this blows up my >> >> code >> >> a lot (browser checks, duplicated code)... >> >> >> >> Thank you very much in advance for changing this :-) >> >> >> >> Greets from Germany, >> >> >> >> Benno Dielmann. >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> Check out the new SourceForge.net Marketplace. >> >> It's the best place to buy or sell services for >> >> just about anything Open Source. >> >> >> >> >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> >> _______________________________________________ >> >> Flexwiki-users mailing list >> >> Flexwiki-users@lists.sourceforge.net >> >> https://lists.sourceforge.net/lists/listinfo/flexwiki-users >> >> >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ >> > Flexwiki-users mailing list >> > Flexwiki-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/flexwiki-users >> > >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Flexwiki-users mailing list >> Flexwiki-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/flexwiki-users >> > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ > Flexwiki-users mailing list > Flexwiki-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flexwiki-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
