Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Page 2 of 2 FirstFirst 12
Results 16 to 20 of 20
  1. #16
    Supreme Master coder! Old Pedant's Avatar
    Join Date
    Feb 2009
    Posts
    25,602
    Thanks
    78
    Thanked 4,387 Times in 4,352 Posts
    Ahhh...good eyes, Xelawho!

    Yes, even Chrome reports the missing </div>, but then it silently tries to make a best guess as to where it should be.

    I don't think IE is wrong in this. When you omit a </div>, all the browser *CAN* do is guess where it should end, and the browser could well guess wrong.

    But this entire page is a horrible mess, HTML-wise.
    http://validator.w3.org/check?uri=ht...Inline&group=0

    So many errors, it's scary. But, indeed, way down in the list we see:
    Line 639, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
    and
    Line 537, Column 5: start tag was here
    <div id="mainWindow" dojotype="dijit.layout.BorderContainer" design="sideba…

    GibbyAR: You *REALLY* should pay attention to the validator and clean up most of those errors. Some will have to remain, because of DOJO, but at least clean up the egregious ones.
    An optimist sees the glass as half full.
    A pessimist sees the glass as half empty.
    A realist drinks it no matter how much there is.

  2. #17
    New to the CF scene
    Join Date
    Jun 2013
    Posts
    9
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Listen, you guys are all rock stars. My sincerest thanks for your patience and sage advice. And thanks for the heads-up about using the validator. I had never seen or used something like that. I have the error count down to 10 this morning. Most of those I have to live with due to the Dojo required by a proprietary API I'm using but they don't appear to be deal breakers.

    Again, many thanks for everyone's help and guidance.

    RG

  3. #18
    Senior Coder xelawho's Avatar
    Join Date
    Nov 2010
    Posts
    2,969
    Thanks
    56
    Thanked 557 Times in 554 Posts
    don't worry too much about the validator - it is very useful for picking up on problems like the one you had, but can be rather schoolmarmish at times. And yes, it knows nothing about dojo, so you will never get rid of those "errors".

    that said, I'd have to agree with the error that's popping at Line 579, Column 26. You're putting a <div> (block level element) inside a span (inline element) which is illegal html, regardless (I believe) of doctype.

    That div just seems to hold the text for the button (maybe?) so you could change it to a span easy enough I think...
    Last edited by xelawho; 06-14-2013 at 03:46 PM.

  4. Users who have thanked xelawho for this post:

    GibbyAR (06-14-2013)

  5. #19
    New to the CF scene
    Join Date
    Jun 2013
    Posts
    9
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by xelawho View Post
    don't worry too much about the validator - it is very useful for picking up on problems like the one you had, but can be rather schoolmarmish at times. And yes, it knows nothing about dojo, so you will never get rid of those "errors".

    that said, I'd have to agree with the error that's popping at Line 579, Column 26. You're putting a <div> (block level element) inside a span (inline element) which is illegal html, regardless (I believe) of doctype.

    That div just seems to hold the text for the button (maybe?) so you could change it to a span easy enough I think...
    Yeah, oddly enough, those are actually pre-defined "containers" if you will for a couple proprietary dijits (esri.dijit.Measurement & esri.dijit.Print) being used to export to PDF and provide a measurement tool.

  6. #20
    Supreme Master coder! Old Pedant's Avatar
    Join Date
    Feb 2009
    Posts
    25,602
    Thanks
    78
    Thanked 4,387 Times in 4,352 Posts
    Quote Originally Posted by GibbyAR View Post
    Yeah, oddly enough, those are actually pre-defined "containers" if you will for a couple proprietary dijits (esri.dijit.Measurement & esri.dijit.Print) being used to export to PDF and provide a measurement tool.
    Oh, not so "oddly". WAY too many supposedly professional JavaScript libraries are full of errors like that. Heck, even the Google Maps API in version 2 had an egregious error like that, and normally Google is fanatic about correctness.
    An optimist sees the glass as half full.
    A pessimist sees the glass as half empty.
    A realist drinks it no matter how much there is.

  7. Users who have thanked Old Pedant for this post:

    GibbyAR (06-14-2013)


 
Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •