On Sep 6, 4:50 am, Klaus Hartl <[EMAIL PROTECTED]> wrote: > Pops wrote: > > Sorry if I am a dounce, but I still don't see the invalidity of it. > > > Do you have an example to show how this is incorrect in relationship > > to anything (DOM? CSS?) ? > > ul and ol elements may only have li elements as children, that's written > in the DTD.http://www.w3.org/TR/html401/struct/lists.html#h-10.2 > > Use the W3C validator to see that this is invalid.http://validator.w3.org/ Thanks, that is what I was looking for. > > The technical problem I see using this wrapping method is that you get > > redundant (bubbling?) events. Is that right? > > Don't know. The technical problem to me is that you shouldn't script on > top of an invalid DOM as you won't get predictable behaviour, especially > cross browser. Well, you do get redundant bubbling using this enclosment method. :-) I see your point, but if you already have "transformations" which may have what one may considered to be invalid for its purposes, but it isn't invalid for other purposes, then many the decision to use this particular form for input is whats wrong :-) I mean I can write a validator that makes it right too :-) If the UL tag offered a title attribute that you wouldn't need a redundant LI wrapping. :-) This started with our XML outlined Help System: <chapter name="Welcome to Wildcat! SDK Development"> <section name="Wildcat! SDK Development News"/> </chapter> <chapter name="Wildcat! SDK Documention"> <chapter name="Visual C/C+ Development"> <chapter name="Reference" page="vc_functions" title="Wildcat! C/C++ SDK Reference"/> <chapter name="Structures" page="vc_structures"/> <chapter name="Samples" page="vc_samples"/> </chapter> <chapter name="Visual Basic Development"> <chapter name="Reference" page="vb_functions" title="Wildcat! Visual BASIC SDK Reference"/> <chapter name="Structures" page="vb_structures"/> <chapter name="Samples" page="vb_samples"/> </chapter> <chapter name="Wildcat! BASIC Development"> <chapter name="Wildcat! Basic Compiler"> <section name="Command Line Compiler"/> <section name="Interactive Development"/> </chapter> <chapter name="Reference" page="wcc_functions" title="wcBASIC SDK Reference"> <chapter name="Implicit Library" page="wcc_implicit_functions" title="wcBASIC Implicit SDK Library"/> <chapter name="Explicit Library" page="wcc_explicit_functions" include="wcbasic_functions.xml" title="wcBASIC Library Modules Reference"/> </chapter> <chapter name="Structures" page="wcc_structures" include="wcbasic_structures.xml"/> <chapter name="Samples" page="wb_samples"/> </chapter> <chapter name="Wildcat! JAVA Development"> <chapter name="Reference" page="java_functions" title="Wildcat! Java SDK Reference"/> <chapter name="Structures" page="java_structures"/> <chapter name="Samples" page="wj_samples"/> </chapter> <chapter name="Visual Foxpro Development"> <chapter name="Reference" page="vfp_functions" title="Wildcat! Visual FoxPro SDK Reference"/> <chapter name="Structures" page="vfp_structures"/> <chapter name="Samples" page="vfp_samples"/> </chapter> <chapter name="Delphi Development"> <chapter name="Reference" page="pas_functions" title="Wildcat! Delphi SDK Reference"/> <chapter name="Structures" page="pas_structures"/> <chapter name="Samples" page="pas_samples"/> </chapter> </chapter> We have a converter that took this and created Windows Help Files. A change to the converter pulled the <OBJECT> activex stuff and what ideally remained were a next UL/LI structure. Now I needed a JavaScript menu creator for this. but first, I played in native form to learn the selectors. In the end, two key things I found: 1) I don't have "valid" construct of UI/LI generator. It was using <LI> without ending </LI> 2) The valid construct produces redundant event propagation because of the LI wrappings. Also the jQuery Plugin TreeView could not handle the size. Too slow. Another one (Non-Jquery) t was more native and worked more snappy. Anyway, I'm working on a jQuery "tree menu" one that isn't going to have all the overhead. Thanks -- HLS
