OK, I solved the worst of it by rearranging the div objects, moving absolute items up to the top of the containers. I have one remaining issue. When expanded and you roll over the h2 tags it fires the mouseleave event (in IE). Any ideas? I think I can solve this by observing the the element rolled over and ignoring h2 items but I'd like to report this as a possible bug before fixing.
Karl.. On Sep 21, 8:13 pm, kstubs <[email protected]> wrote: > OK, I've been through and cleaned up a number of the issues. If the > remaining issues seem to be the culprit to such miss behaviors in IE, > please let me know. Otherwise, I'm going to assume that the issues > are related to unsupported (or miss-supported) CSS in IE. > Any help would be great! > > Karl.. > > On Sep 21, 5:32 am, Richard Quadling <[email protected]> wrote: > > > > >http://validator.w3.org/check?uri=http://www.meetscoresonline.com/res... > > > You have some errors here. Not all are important but some I'd be worried > > about. > > > character data is not allowed here ✉ > > You have used character data somewhere it is not permitted to appear. > > Mistakes that can cause this error include: > > > putting text directly in the body of the document without wrapping it > > in a container element (such as a <p>aragraph</p>), or > > forgetting to quote an attribute value (where characters such as "%" > > and "/" are common, but cannot appear without surrounding quotes), or > > using XHTML-style self-closing tags (such as <meta ... />) in HTML > > 4.01 or earlier. To fix, remove the extra slash ('/') character. For > > more information about the reasons for this, see Empty elements in > > SGML, HTML, XML, and XHTML. > > Line 88, column 9: character data is not allowed here > > How to Contact MSO > > document type does not allow element X here; assuming missing Y start-tag ✉ > > Line 120, column 18: document type does not allow element "OL" here; > > assuming missing "LI" start-tag > > <ol> > > end tag for X which is not finished ✉ > > Most likely, you nested tags and closed them in the wrong order. For > > example <p><em>...</p> is not acceptable, as <em> must be closed > > before <p>. Acceptable nesting is: <p><em>...</em></p> > > > Another possibility is that you used an element which requires a child > > element that you did not include. Hence the parent element is "not > > finished", not complete. For instance, in HTML the <head> element must > > contain a <title> child element, lists require appropriate list items > > (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on. > > > Line 71, column 36: end tag for "UL" which is not finished > > <ul class="result"></ul> > > Line 202, column 85: end tag for "UL" which is not finished > > … <ul id="level_picker" class="sub_menu level" > > style="display:none"></ul> > > Line 204, column 91: end tag for "UL" which is not finished > > … <ul id="division_picker" class="sub_menu division" > > style="display:none"></ul> > > > And > > > Character Encoding mismatch! > > > The character encoding specified in the HTTP header (utf-8) is > > different from the value in the <meta> element (utf-16). I will use > > the value from the HTTP header (utf-8) for this validation. > > > Line 120, Column 18: document type does not allow element "OL" here; > > assuming missing "LI" start-tag > > <ol> > > > -- > > Richard Quadling > > Twitter : EE : Zend > > @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
