Loading ...
Sorry, an error occurred while loading the content.

RE: [ydn-javascript] XHTML Support

Expand Messages
  • Jason Lee
    Right. That s the issue I m fighting, and it appears to be due to the use of   (in FF only). Using   resolves the isssue. Take a look at the same
    Message 1 of 23 , Nov 1, 2006
    • 0 Attachment
      Right. That's the issue I'm fighting, and it appears to be due to the
      use of   (in FF only). Using   resolves the isssue. Take a
      look at the same line in
      http://blogs.steeplesoft.com/cal/calendar-fixed.js.

      -----
      Jason Lee, SCJP
      Programmer/Analyst
      http://www.iec-okc.com


      > -----Original Message-----
      > From: ydn-javascript@yahoogroups.com
      > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of
      > foti-1@...
      > Sent: Wednesday, November 01, 2006 3:13 PM
      > To: ydn-javascript@yahoogroups.com
      > Subject: RE: [ydn-javascript] XHTML Support
      >
      > Firebug reports:
      >
      > XML Parsing Error: undefined entity Location: Line Number 1,
      > Column 41:
      > uncaught exception: [Exception... "An invalid or illegal
      > string was specified" code: "12" nsresult: "0x8053000c
      > (NS_ERROR_DOM_SYNTAX_ERR)" location:
      > "http://blogs.steeplesoft.com/cal/calendar-orig.js Line: 2179"]
      >
      > Which is this line:
      > this.linkLeft.innerHTML = " ";
      >
      >
      > -------------- Original message ----------------------
      > From: "Jason Lee" <lee@...>
      > > Ok. I finally have a small test case to reproduce. I think the
      > > problem is the use of   in calendar.js. If I replace
      >   with
      > >   the problem goes away. Look here:
      > >
      > > http://blogs.steeplesoft.com/cal/
      > >
      > > The important files are the XHTML links. They're basic XHTML files
      > > with the .xhtml ending to force Apache to send the XHTML
      > mime type.
      > > The HTML files are symlinks to the .xhtml files, but with .html
      > > suffixes to force the HTML mime type. Same files. Different mime
      > > types. Different results. The "fixed" column has the
      > entity change, while the "broken"
      > > column has the calendar.js straight from the 0.11.4 archive.
      > >
      > > It's also interesting to note that, while the "fixed"
      > version renders,
      > > it's pretty ugly and unusable in Firefox, but looks as
      > expected in IE.
      > > While that's not directly related to the issue at hand, if
      > anyone has
      > > any suggestions for fixing that, I'm all ears.
      > >
      > > Thanks!
      > >
      > > -----
      > > Jason Lee, SCJP
      > > Programmer/Analyst
      > > http://www.iec-okc.com
      > >
      > >
      > > > -----Original Message-----
      > > > From: ydn-javascript@yahoogroups.com
      > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Matt Sweeney
      > > > Sent: Wednesday, October 25, 2006 1:51 PM
      > > > To: ydn-javascript@yahoogroups.com
      > > > Subject: Re: [ydn-javascript] XHTML Support
      > > >
      > > > Hi Jason,
      > > >
      > > > Can you provide a working repro of your issue? This works in my
      > > > simple test case (sending "Content-Type:
      > > > application/xhtml+xml" header).
      > > >
      > > > Thanks,
      > > >
      > > > Matt
      > > >
      > > > Jason Lee wrote:
      > > >
      > > > >I don't have specifics, but here's where it's biting me:
      > > > >
      > > > > <img id="img_j_id10" ... />
      > > > >...
      > > > > var pos = YAHOO.util.Dom.getXY("img_j_id10");
      > > > >
      > > > >fails, where
      > > > >
      > > > > document.getElementById("img_j_id10");
      > > > >
      > > > >does not. If I put the exact same HTML and JS code in a .html
      > > > >document, it works fine. In digging to find the issue, I
      > > > ran across a
      > > > >blog that indicated an XHTML issue. Given the only change that
      > > > >occurred between working and non-working pages was the
      > > > switch to XHTML,
      > > > >I'm assuming they're related. I'd be more than happy to
      > be proven
      > > > >wrong, though. :)
      > > > >
      > > > >-----
      > > > >Jason Lee, SCJP
      > > > >Programmer/Analyst
      > > > >http://www.iec-okc.com <http://www.iec-okc.com/>
      > > > >
      > > > >
      > > > >
      > > > >________________________________
      > > > >
      > > > > From: ydn-javascript@yahoogroups.com
      > > > >[mailto:ydn-javascript@yahoogroups.com] On Behalf Of
      > Tony Summerville
      > > > > Sent: Wednesday, October 25, 2006 9:55 AM
      > > > > To: ydn-javascript@yahoogroups.com
      > > > > Subject: Re: [ydn-javascript] XHTML Support
      > > > >
      > > > >
      > > > > What specific issues does YUI have with XHTML pages?
      > > > >
      > > > >
      > > > > On 10/25/06, Jason Lee <lee@...> wrote:
      > > > >
      > > > > I found out the hard way
      > > > yesterday the YUI has issues with XHTML
      > > > >pages, but that support for that is being worked on. Any
      > > > word on how
      > > > >close that is?
      > > > >
      > > > > Semi-related, is there a public repo from which
      > > > we can pull nightly
      > > > >snapshots? Public issue tracker, etc? I haven't been
      > able to find
      > > > >either thus far...
      > > > >
      > > > > -----
      > > > > Jason Lee, SCJP
      > > > > Programmer/Analyst
      > > > > http://www.iec-okc.com <http://www.iec-okc.com/>
      > > > >
      > > > >
      > > > >
      > > > >
      > > > >Yahoo! Groups Links
      > > > >
      > > > >
      > > > >
      > > > >
      > > > >
      > > > >
      > > > >
      > > > >
      > > >
      > > >
      > > >
      > > >
      > > > Yahoo! Groups Links
      > > >
      > > >
      > > >
      > > >
      > > >
      > >
      >
      >
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
    • Josh Peters
      ... It s definitely a named entity error. I m also experiencing some serious bugs with createElement using uppercase node names. Changing everything to
      Message 2 of 23 , Nov 2, 2006
      • 0 Attachment
        On 11/1/06, Jason Lee <lee@...> wrote:
        > Right. That's the issue I'm fighting, and it appears to be due to the
        > use of   (in FF only). Using   resolves the isssue. Take a
        > look at the same line in
        > http://blogs.steeplesoft.com/cal/calendar-fixed.js.

        It's definitely a named entity error. I'm also experiencing some
        serious bugs with createElement using uppercase node names. Changing
        everything to lowercase works properly. I've submitted a patch to the
        YUI sourceforge site explaining the changes that needed to be made.

        There's a much larger issue to be dealt with across all of YUI though.
        It seems that ANY node names need to be lower case in order to
        function properly throughout any application/xhtml+xml mime type
        pages.

        Any calls to getElementsByTagName and createElement need lower case
        parameters if they are to work in pages served as
        application/xhtml+xml.

        Good catch.

        > > -----Original Message-----
        > > From: ydn-javascript@yahoogroups.com
        > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of
        > > foti-1@...
        > > Sent: Wednesday, November 01, 2006 3:13 PM
        > > To: ydn-javascript@yahoogroups.com
        > > Subject: RE: [ydn-javascript] XHTML Support
        > >
        >
        > > Firebug reports:
        > >
        > > XML Parsing Error: undefined entity Location: Line Number 1,
        > > Column 41:
        > > uncaught exception: [Exception... "An invalid or illegal
        > > string was specified" code: "12" nsresult: "0x8053000c
        > > (NS_ERROR_DOM_SYNTAX_ERR)" location:
        > > "http://blogs.steeplesoft.com/cal/calendar-orig.js Line: 2179"]
        > >
        > > Which is this line:
        > > this.linkLeft.innerHTML = " ";
        > >
        > >
        > > -------------- Original message ----------------------
        > > From: "Jason Lee" <lee@...>
        > > > Ok. I finally have a small test case to reproduce. I think the
        > > > problem is the use of   in calendar.js. If I replace
        > >   with
        > > >   the problem goes away. Look here:
        > > >
        > > > http://blogs.steeplesoft.com/cal/
        > > >
        > > > The important files are the XHTML links. They're basic XHTML files
        > > > with the .xhtml ending to force Apache to send the XHTML
        > > mime type.
        > > > The HTML files are symlinks to the .xhtml files, but with .html
        > > > suffixes to force the HTML mime type. Same files. Different mime
        > > > types. Different results. The "fixed" column has the
        > > entity change, while the "broken"
        > > > column has the calendar.js straight from the 0.11.4 archive.
        > > >
        > > > It's also interesting to note that, while the "fixed"
        > > version renders,
        > > > it's pretty ugly and unusable in Firefox, but looks as
        > > expected in IE.
        > > > While that's not directly related to the issue at hand, if
        > > anyone has
        > > > any suggestions for fixing that, I'm all ears.
        > > >
        > > > Thanks!
        > > >
        > > > -----
        > > > Jason Lee, SCJP
        > > > Programmer/Analyst
        > > > http://www.iec-okc.com
        > > >
        > > >
        > > > > -----Original Message-----
        > > > > From: ydn-javascript@yahoogroups.com
        > > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Matt Sweeney
        > > > > Sent: Wednesday, October 25, 2006 1:51 PM
        > > > > To: ydn-javascript@yahoogroups.com
        > > > > Subject: Re: [ydn-javascript] XHTML Support
        > > > >
        > > > > Hi Jason,
        > > > >
        > > > > Can you provide a working repro of your issue? This works in my
        > > > > simple test case (sending "Content-Type:
        > > > > application/xhtml+xml" header).
        > > > >
        > > > > Thanks,
        > > > >
        > > > > Matt
        > > > >
        > > > > Jason Lee wrote:
        > > > >
        > > > > >I don't have specifics, but here's where it's biting me:
        > > > > >
        > > > > > <img id="img_j_id10" ... />
        > > > > >...
        > > > > > var pos = YAHOO.util.Dom.getXY("img_j_id10");
        > > > > >
        > > > > >fails, where
        > > > > >
        > > > > > document.getElementById("img_j_id10");
        > > > > >
        > > > > >does not. If I put the exact same HTML and JS code in a .html
        > > > > >document, it works fine. In digging to find the issue, I
        > > > > ran across a
        > > > > >blog that indicated an XHTML issue. Given the only change that
        > > > > >occurred between working and non-working pages was the
        > > > > switch to XHTML,
        > > > > >I'm assuming they're related. I'd be more than happy to
        > > be proven
        > > > > >wrong, though. :)
        > > > > >
        > > > > >-----
        > > > > >Jason Lee, SCJP
        > > > > >Programmer/Analyst
        > > > > >http://www.iec-okc.com <http://www.iec-okc.com/>
        > > > > >
        > > > > >
        > > > > >
        > > > > >________________________________
        > > > > >
        > > > > > From: ydn-javascript@yahoogroups.com
        > > > > >[mailto:ydn-javascript@yahoogroups.com] On Behalf Of
        > > Tony Summerville
        > > > > > Sent: Wednesday, October 25, 2006 9:55 AM
        > > > > > To: ydn-javascript@yahoogroups.com
        > > > > > Subject: Re: [ydn-javascript] XHTML Support
        > > > > >
        > > > > >
        > > > > > What specific issues does YUI have with XHTML pages?
        > > > > >
        > > > > >
        > > > > > On 10/25/06, Jason Lee <lee@...> wrote:
        > > > > >
        > > > > > I found out the hard way
        > > > > yesterday the YUI has issues with XHTML
        > > > > >pages, but that support for that is being worked on. Any
        > > > > word on how
        > > > > >close that is?
        > > > > >
        > > > > > Semi-related, is there a public repo from which
        > > > > we can pull nightly
        > > > > >snapshots? Public issue tracker, etc? I haven't been
        > > able to find
        > > > > >either thus far...
        > > > > >
        > > > > > -----
        > > > > > Jason Lee, SCJP
        > > > > > Programmer/Analyst
        > > > > > http://www.iec-okc.com <http://www.iec-okc.com/>
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > > >Yahoo! Groups Links
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > > >
        > > > >
        > > > >
        > > > >
        > > > >
        > > > > Yahoo! Groups Links
        > > > >
        > > > >
        > > > >
        > > > >
        > > > >
        > > >
        > >
        > >
        > >
        > >
        > >
        > > Yahoo! Groups Links
        > >
        > >
        > >
        > >
        >
        >
        >
      • Josh Peters
        Okay, I ve submitted a patch fixing all 12! spots in YUI 0.11.4 where XHTML bugs will occur.
        Message 3 of 23 , Nov 2, 2006
        • 0 Attachment
          Okay, I've submitted a patch fixing all 12! spots in YUI 0.11.4 where
          XHTML bugs will occur.

          https://sourceforge.net/tracker/index.php?func=detail&aid=1589408&group_id=165715&atid=836478

          Hope this helps (and gets accepted into YUI for 0.11.5).

          On 11/2/06, Josh Peters <jcpeters@...> wrote:
          > On 11/1/06, Jason Lee <lee@...> wrote:
          > > Right. That's the issue I'm fighting, and it appears to be due to the
          > > use of   (in FF only). Using   resolves the isssue. Take a
          > > look at the same line in
          > > http://blogs.steeplesoft.com/cal/calendar-fixed.js.
          >
          > It's definitely a named entity error. I'm also experiencing some
          > serious bugs with createElement using uppercase node names. Changing
          > everything to lowercase works properly. I've submitted a patch to the
          > YUI sourceforge site explaining the changes that needed to be made.
          >
          > There's a much larger issue to be dealt with across all of YUI though.
          > It seems that ANY node names need to be lower case in order to
          > function properly throughout any application/xhtml+xml mime type
          > pages.
          >
          > Any calls to getElementsByTagName and createElement need lower case
          > parameters if they are to work in pages served as
          > application/xhtml+xml.
          >
          > Good catch.
          >
          > > > -----Original Message-----
          > > > From: ydn-javascript@yahoogroups.com
          > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of
          > > > foti-1@...
          > > > Sent: Wednesday, November 01, 2006 3:13 PM
          > > > To: ydn-javascript@yahoogroups.com
          > > > Subject: RE: [ydn-javascript] XHTML Support
          > > >
          > >
          > > > Firebug reports:
          > > >
          > > > XML Parsing Error: undefined entity Location: Line Number 1,
          > > > Column 41:
          > > > uncaught exception: [Exception... "An invalid or illegal
          > > > string was specified" code: "12" nsresult: "0x8053000c
          > > > (NS_ERROR_DOM_SYNTAX_ERR)" location:
          > > > "http://blogs.steeplesoft.com/cal/calendar-orig.js Line: 2179"]
          > > >
          > > > Which is this line:
          > > > this.linkLeft.innerHTML = " ";
          > > >
          > > >
          > > > -------------- Original message ----------------------
          > > > From: "Jason Lee" <lee@...>
          > > > > Ok. I finally have a small test case to reproduce. I think the
          > > > > problem is the use of   in calendar.js. If I replace
          > > >   with
          > > > >   the problem goes away. Look here:
          > > > >
          > > > > http://blogs.steeplesoft.com/cal/
          > > > >
          > > > > The important files are the XHTML links. They're basic XHTML files
          > > > > with the .xhtml ending to force Apache to send the XHTML
          > > > mime type.
          > > > > The HTML files are symlinks to the .xhtml files, but with .html
          > > > > suffixes to force the HTML mime type. Same files. Different mime
          > > > > types. Different results. The "fixed" column has the
          > > > entity change, while the "broken"
          > > > > column has the calendar.js straight from the 0.11.4 archive.
          > > > >
          > > > > It's also interesting to note that, while the "fixed"
          > > > version renders,
          > > > > it's pretty ugly and unusable in Firefox, but looks as
          > > > expected in IE.
          > > > > While that's not directly related to the issue at hand, if
          > > > anyone has
          > > > > any suggestions for fixing that, I'm all ears.
          > > > >
          > > > > Thanks!
          > > > >
          > > > > -----
          > > > > Jason Lee, SCJP
          > > > > Programmer/Analyst
          > > > > http://www.iec-okc.com
          > > > >
          > > > >
          > > > > > -----Original Message-----
          > > > > > From: ydn-javascript@yahoogroups.com
          > > > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Matt Sweeney
          > > > > > Sent: Wednesday, October 25, 2006 1:51 PM
          > > > > > To: ydn-javascript@yahoogroups.com
          > > > > > Subject: Re: [ydn-javascript] XHTML Support
          > > > > >
          > > > > > Hi Jason,
          > > > > >
          > > > > > Can you provide a working repro of your issue? This works in my
          > > > > > simple test case (sending "Content-Type:
          > > > > > application/xhtml+xml" header).
          > > > > >
          > > > > > Thanks,
          > > > > >
          > > > > > Matt
          > > > > >
          > > > > > Jason Lee wrote:
          > > > > >
          > > > > > >I don't have specifics, but here's where it's biting me:
          > > > > > >
          > > > > > > <img id="img_j_id10" ... />
          > > > > > >...
          > > > > > > var pos = YAHOO.util.Dom.getXY("img_j_id10");
          > > > > > >
          > > > > > >fails, where
          > > > > > >
          > > > > > > document.getElementById("img_j_id10");
          > > > > > >
          > > > > > >does not. If I put the exact same HTML and JS code in a .html
          > > > > > >document, it works fine. In digging to find the issue, I
          > > > > > ran across a
          > > > > > >blog that indicated an XHTML issue. Given the only change that
          > > > > > >occurred between working and non-working pages was the
          > > > > > switch to XHTML,
          > > > > > >I'm assuming they're related. I'd be more than happy to
          > > > be proven
          > > > > > >wrong, though. :)
          > > > > > >
          > > > > > >-----
          > > > > > >Jason Lee, SCJP
          > > > > > >Programmer/Analyst
          > > > > > >http://www.iec-okc.com <http://www.iec-okc.com/>
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >________________________________
          > > > > > >
          > > > > > > From: ydn-javascript@yahoogroups.com
          > > > > > >[mailto:ydn-javascript@yahoogroups.com] On Behalf Of
          > > > Tony Summerville
          > > > > > > Sent: Wednesday, October 25, 2006 9:55 AM
          > > > > > > To: ydn-javascript@yahoogroups.com
          > > > > > > Subject: Re: [ydn-javascript] XHTML Support
          > > > > > >
          > > > > > >
          > > > > > > What specific issues does YUI have with XHTML pages?
          > > > > > >
          > > > > > >
          > > > > > > On 10/25/06, Jason Lee <lee@...> wrote:
          > > > > > >
          > > > > > > I found out the hard way
          > > > > > yesterday the YUI has issues with XHTML
          > > > > > >pages, but that support for that is being worked on. Any
          > > > > > word on how
          > > > > > >close that is?
          > > > > > >
          > > > > > > Semi-related, is there a public repo from which
          > > > > > we can pull nightly
          > > > > > >snapshots? Public issue tracker, etc? I haven't been
          > > > able to find
          > > > > > >either thus far...
          > > > > > >
          > > > > > > -----
          > > > > > > Jason Lee, SCJP
          > > > > > > Programmer/Analyst
          > > > > > > http://www.iec-okc.com <http://www.iec-okc.com/>
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >Yahoo! Groups Links
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > > >
          > > > > >
          > > > > >
          > > > > >
          > > > > >
          > > > > > Yahoo! Groups Links
          > > > > >
          > > > > >
          > > > > >
          > > > > >
          > > > > >
          > > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > > Yahoo! Groups Links
          > > >
          > > >
          > > >
          > > >
          > >
          > >
          > >
          >
        • Jason Lee
          Ah! The bug tracker! Thanks. :) ... Jason Lee, SCJP Programmer/Analyst http://www.iec-okc.com
          Message 4 of 23 , Nov 2, 2006
          • 0 Attachment
            Ah! The bug tracker! Thanks. :)

            -----
            Jason Lee, SCJP
            Programmer/Analyst
            http://www.iec-okc.com


            > -----Original Message-----
            > From: ydn-javascript@yahoogroups.com
            > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Josh Peters
            > Sent: Thursday, November 02, 2006 12:04 PM
            > To: ydn-javascript@yahoogroups.com
            > Subject: Re: [ydn-javascript] XHTML Support
            >
            > Okay, I've submitted a patch fixing all 12! spots in YUI
            > 0.11.4 where XHTML bugs will occur.
            >
            > https://sourceforge.net/tracker/index.php?func=detail&aid=1589
            > 408&group_id=165715&atid=836478
            >
            > Hope this helps (and gets accepted into YUI for 0.11.5).
            >
            > On 11/2/06, Josh Peters <jcpeters@...> wrote:
            > > On 11/1/06, Jason Lee <lee@...> wrote:
            > > > Right. That's the issue I'm fighting, and it appears to
            > be due to
            > > > the use of   (in FF only). Using   resolves
            > the isssue.
            > > > Take a look at the same line in
            > > > http://blogs.steeplesoft.com/cal/calendar-fixed.js.
            > >
            > > It's definitely a named entity error. I'm also experiencing some
            > > serious bugs with createElement using uppercase node names.
            > Changing
            > > everything to lowercase works properly. I've submitted a
            > patch to the
            > > YUI sourceforge site explaining the changes that needed to be made.
            > >
            > > There's a much larger issue to be dealt with across all of
            > YUI though.
            > > It seems that ANY node names need to be lower case in order to
            > > function properly throughout any application/xhtml+xml mime type
            > > pages.
            > >
            > > Any calls to getElementsByTagName and createElement need lower case
            > > parameters if they are to work in pages served as
            > > application/xhtml+xml.
            > >
            > > Good catch.
            > >
            > > > > -----Original Message-----
            > > > > From: ydn-javascript@yahoogroups.com >
            > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of >
            > > > foti-1@... > Sent: Wednesday, November 01, 2006
            > 3:13 PM >
            > > > To: ydn-javascript@yahoogroups.com > Subject: RE:
            > [ydn-javascript]
            > > > XHTML Support >
            > > >
            > > > > Firebug reports:
            > > > >
            > > > > XML Parsing Error: undefined entity Location: Line
            > Number 1, >
            > > > Column 41:
            > > > > uncaught exception: [Exception... "An invalid or illegal >
            > > > string was specified" code: "12" nsresult: "0x8053000c >
            > > > (NS_ERROR_DOM_SYNTAX_ERR)" location:
            > > > > "http://blogs.steeplesoft.com/cal/calendar-orig.js
            > Line: 2179"]
            > > > > > Which is this line:
            > > > > this.linkLeft.innerHTML = " "; > > > --------------
            > > > Original message ---------------------- > From: "Jason Lee"
            > > > <lee@...> > > Ok. I finally have a small test case to
            > > > reproduce. I think the > > problem is the use of   in
            > > > calendar.js. If I replace >   with > >   the problem
            > > > goes away. Look here:
            > > > > >
            > > > > > http://blogs.steeplesoft.com/cal/ > > > > The
            > important files
            > > > are the XHTML links. They're basic XHTML files > > with
            > the .xhtml
            > > > ending to force Apache to send the XHTML > mime type.
            > > > > > The HTML files are symlinks to the .xhtml files, but
            > with .html
            > > > > > suffixes to force the HTML mime type. Same files. Different
            > > > mime > > types. Different results. The "fixed" column
            > has the >
            > > > entity change, while the "broken"
            > > > > > column has the calendar.js straight from the 0.11.4 archive.
            > > > > >
            > > > > > It's also interesting to note that, while the "fixed"
            > > > > version renders,
            > > > > > it's pretty ugly and unusable in Firefox, but looks as >
            > > > expected in IE.
            > > > > > While that's not directly related to the issue at
            > hand, if >
            > > > anyone has > > any suggestions for fixing that, I'm all ears.
            > > > > >
            > > > > > Thanks!
            > > > > >
            > > > > > -----
            > > > > > Jason Lee, SCJP
            > > > > > Programmer/Analyst
            > > > > > http://www.iec-okc.com
            > > > > >
            > > > > >
            > > > > > > -----Original Message-----
            > > > > > > From: ydn-javascript@yahoogroups.com > > >
            > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Matt
            > Sweeney >
            > > > > > Sent: Wednesday, October 25, 2006 1:51 PM > > > To:
            > > > ydn-javascript@yahoogroups.com > > > Subject: Re:
            > [ydn-javascript]
            > > > XHTML Support > > > > > > Hi Jason, > > > > > > Can
            > you provide
            > > > a working repro of your issue? This works in my > > >
            > simple test
            > > > case (sending "Content-Type:
            > > > > > > application/xhtml+xml" header).
            > > > > > >
            > > > > > > Thanks,
            > > > > > >
            > > > > > > Matt
            > > > > > >
            > > > > > > Jason Lee wrote:
            > > > > > >
            > > > > > > >I don't have specifics, but here's where it's biting me:
            > > > > > > >
            > > > > > > > <img id="img_j_id10" ... />
            > > > > > > >...
            > > > > > > > var pos = YAHOO.util.Dom.getXY("img_j_id10");
            > > > > > > >
            > > > > > > >fails, where
            > > > > > > >
            > > > > > > > document.getElementById("img_j_id10");
            > > > > > > >
            > > > > > > >does not. If I put the exact same HTML and JS code in a
            > > > .html > > > >document, it works fine. In digging to find the
            > > > issue, I > > > ran across a > > > >blog that indicated an XHTML
            > > > issue. Given the only change that > > > >occurred
            > between working
            > > > and non-working pages was the > > > switch to XHTML, > > > >I'm
            > > > assuming they're related. I'd be more than happy to >
            > be proven >
            > > > > > >wrong, though. :) > > > > > > > >----- > > > >Jason Lee,
            > > > SCJP > > > >Programmer/Analyst > > > >http://www.iec-okc.com
            > > > <http://www.iec-okc.com/> > > > > > > > > > > > > > > >
            > > > >________________________________ > > > >
            > > > > > > > From: ydn-javascript@yahoogroups.com
            > > > > > > >[mailto:ydn-javascript@yahoogroups.com] On Behalf
            > Of > Tony
            > > > Summerville
            > > > > > > > Sent: Wednesday, October 25, 2006 9:55 AM
            > > > > > > > To: ydn-javascript@yahoogroups.com
            > > > > > > > Subject: Re: [ydn-javascript] XHTML Support
            > > > > > > >
            > > > > > > >
            > > > > > > > What specific issues does YUI have with XHTML pages?
            > > > > > > >
            > > > > > > >
            > > > > > > > On 10/25/06, Jason Lee <lee@...> wrote:
            > > > > > > >
            > > > > > > > I found out the hard way
            > > > > > > yesterday the YUI has issues with XHTML > > > >pages, but
            > > > that support for that is being worked on. Any > > >
            > word on how >
            > > > > > >close that is?
            > > > > > > >
            > > > > > > > Semi-related, is there a public
            > repo from which
            > > > > > > we can pull nightly
            > > > > > > >snapshots? Public issue tracker, etc? I haven't been >
            > > > able to find > > > >either thus far...
            > > > > > > >
            > > > > > > > -----
            > > > > > > > Jason Lee, SCJP
            > > > > > > > Programmer/Analyst
            > > > > > > > http://www.iec-okc.com
            > <http://www.iec-okc.com/>
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >Yahoo! Groups Links
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > > >
            > > > > > >
            > > > > > >
            > > > > > >
            > > > > > >
            > > > > > > Yahoo! Groups Links
            > > > > > >
            > > > > > >
            > > > > > >
            > > > > > >
            > > > > > >
            > > > > >
            > > > >
            > > > >
            > > > >
            > > > >
            > > > >
            > > > > Yahoo! Groups Links
            > > > >
            > > > >
            > > > >
            > > > >
            > > >
            > > >
            > > >
            > >
            >
            >
            >
            > Yahoo! Groups Links
            >
            >
            >
            >
            >
          • Jason Lee
            FWIW, I applied your patches to my copy of calendar.js and that resolved all my issues. I sure hope they put this in 0.11.5. Thanks for your help! :) ...
            Message 5 of 23 , Nov 2, 2006
            • 0 Attachment
              FWIW, I applied your patches to my copy of calendar.js and that resolved
              all my issues. I sure hope they put this in 0.11.5. Thanks for your
              help! :)

              -----
              Jason Lee, SCJP
              Programmer/Analyst
              http://www.iec-okc.com


              > -----Original Message-----
              > From: ydn-javascript@yahoogroups.com
              > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Josh Peters
              > Sent: Thursday, November 02, 2006 12:04 PM
              > To: ydn-javascript@yahoogroups.com
              > Subject: Re: [ydn-javascript] XHTML Support
              >
              > Okay, I've submitted a patch fixing all 12! spots in YUI
              > 0.11.4 where XHTML bugs will occur.
              >
              > https://sourceforge.net/tracker/index.php?func=detail&aid=1589
              > 408&group_id=165715&atid=836478
              >
              > Hope this helps (and gets accepted into YUI for 0.11.5).
              >
              > On 11/2/06, Josh Peters <jcpeters@...> wrote:
              > > On 11/1/06, Jason Lee <lee@...> wrote:
              > > > Right. That's the issue I'm fighting, and it appears to
              > be due to
              > > > the use of   (in FF only). Using   resolves
              > the isssue.
              > > > Take a look at the same line in
              > > > http://blogs.steeplesoft.com/cal/calendar-fixed.js.
              > >
              > > It's definitely a named entity error. I'm also experiencing some
              > > serious bugs with createElement using uppercase node names.
              > Changing
              > > everything to lowercase works properly. I've submitted a
              > patch to the
              > > YUI sourceforge site explaining the changes that needed to be made.
              > >
              > > There's a much larger issue to be dealt with across all of
              > YUI though.
              > > It seems that ANY node names need to be lower case in order to
              > > function properly throughout any application/xhtml+xml mime type
              > > pages.
              > >
              > > Any calls to getElementsByTagName and createElement need lower case
              > > parameters if they are to work in pages served as
              > > application/xhtml+xml.
              > >
              > > Good catch.
              > >
              > > > > -----Original Message-----
              > > > > From: ydn-javascript@yahoogroups.com >
              > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of >
              > > > foti-1@... > Sent: Wednesday, November 01, 2006
              > 3:13 PM >
              > > > To: ydn-javascript@yahoogroups.com > Subject: RE:
              > [ydn-javascript]
              > > > XHTML Support >
              > > >
              > > > > Firebug reports:
              > > > >
              > > > > XML Parsing Error: undefined entity Location: Line
              > Number 1, >
              > > > Column 41:
              > > > > uncaught exception: [Exception... "An invalid or illegal >
              > > > string was specified" code: "12" nsresult: "0x8053000c >
              > > > (NS_ERROR_DOM_SYNTAX_ERR)" location:
              > > > > "http://blogs.steeplesoft.com/cal/calendar-orig.js
              > Line: 2179"]
              > > > > > Which is this line:
              > > > > this.linkLeft.innerHTML = " "; > > > --------------
              > > > Original message ---------------------- > From: "Jason Lee"
              > > > <lee@...> > > Ok. I finally have a small test case to
              > > > reproduce. I think the > > problem is the use of   in
              > > > calendar.js. If I replace >   with > >   the problem
              > > > goes away. Look here:
              > > > > >
              > > > > > http://blogs.steeplesoft.com/cal/ > > > > The
              > important files
              > > > are the XHTML links. They're basic XHTML files > > with
              > the .xhtml
              > > > ending to force Apache to send the XHTML > mime type.
              > > > > > The HTML files are symlinks to the .xhtml files, but
              > with .html
              > > > > > suffixes to force the HTML mime type. Same files. Different
              > > > mime > > types. Different results. The "fixed" column
              > has the >
              > > > entity change, while the "broken"
              > > > > > column has the calendar.js straight from the 0.11.4 archive.
              > > > > >
              > > > > > It's also interesting to note that, while the "fixed"
              > > > > version renders,
              > > > > > it's pretty ugly and unusable in Firefox, but looks as >
              > > > expected in IE.
              > > > > > While that's not directly related to the issue at
              > hand, if >
              > > > anyone has > > any suggestions for fixing that, I'm all ears.
              > > > > >
              > > > > > Thanks!
              > > > > >
              > > > > > -----
              > > > > > Jason Lee, SCJP
              > > > > > Programmer/Analyst
              > > > > > http://www.iec-okc.com
              > > > > >
              > > > > >
              > > > > > > -----Original Message-----
              > > > > > > From: ydn-javascript@yahoogroups.com > > >
              > > > [mailto:ydn-javascript@yahoogroups.com] On Behalf Of Matt
              > Sweeney >
              > > > > > Sent: Wednesday, October 25, 2006 1:51 PM > > > To:
              > > > ydn-javascript@yahoogroups.com > > > Subject: Re:
              > [ydn-javascript]
              > > > XHTML Support > > > > > > Hi Jason, > > > > > > Can
              > you provide
              > > > a working repro of your issue? This works in my > > >
              > simple test
              > > > case (sending "Content-Type:
              > > > > > > application/xhtml+xml" header).
              > > > > > >
              > > > > > > Thanks,
              > > > > > >
              > > > > > > Matt
              > > > > > >
              > > > > > > Jason Lee wrote:
              > > > > > >
              > > > > > > >I don't have specifics, but here's where it's biting me:
              > > > > > > >
              > > > > > > > <img id="img_j_id10" ... />
              > > > > > > >...
              > > > > > > > var pos = YAHOO.util.Dom.getXY("img_j_id10");
              > > > > > > >
              > > > > > > >fails, where
              > > > > > > >
              > > > > > > > document.getElementById("img_j_id10");
              > > > > > > >
              > > > > > > >does not. If I put the exact same HTML and JS code in a
              > > > .html > > > >document, it works fine. In digging to find the
              > > > issue, I > > > ran across a > > > >blog that indicated an XHTML
              > > > issue. Given the only change that > > > >occurred
              > between working
              > > > and non-working pages was the > > > switch to XHTML, > > > >I'm
              > > > assuming they're related. I'd be more than happy to >
              > be proven >
              > > > > > >wrong, though. :) > > > > > > > >----- > > > >Jason Lee,
              > > > SCJP > > > >Programmer/Analyst > > > >http://www.iec-okc.com
              > > > <http://www.iec-okc.com/> > > > > > > > > > > > > > > >
              > > > >________________________________ > > > >
              > > > > > > > From: ydn-javascript@yahoogroups.com
              > > > > > > >[mailto:ydn-javascript@yahoogroups.com] On Behalf
              > Of > Tony
              > > > Summerville
              > > > > > > > Sent: Wednesday, October 25, 2006 9:55 AM
              > > > > > > > To: ydn-javascript@yahoogroups.com
              > > > > > > > Subject: Re: [ydn-javascript] XHTML Support
              > > > > > > >
              > > > > > > >
              > > > > > > > What specific issues does YUI have with XHTML pages?
              > > > > > > >
              > > > > > > >
              > > > > > > > On 10/25/06, Jason Lee <lee@...> wrote:
              > > > > > > >
              > > > > > > > I found out the hard way
              > > > > > > yesterday the YUI has issues with XHTML > > > >pages, but
              > > > that support for that is being worked on. Any > > >
              > word on how >
              > > > > > >close that is?
              > > > > > > >
              > > > > > > > Semi-related, is there a public
              > repo from which
              > > > > > > we can pull nightly
              > > > > > > >snapshots? Public issue tracker, etc? I haven't been >
              > > > able to find > > > >either thus far...
              > > > > > > >
              > > > > > > > -----
              > > > > > > > Jason Lee, SCJP
              > > > > > > > Programmer/Analyst
              > > > > > > > http://www.iec-okc.com
              > <http://www.iec-okc.com/>
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >Yahoo! Groups Links
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > > >
              > > > > > >
              > > > > > >
              > > > > > >
              > > > > > >
              > > > > > > Yahoo! Groups Links
              > > > > > >
              > > > > > >
              > > > > > >
              > > > > > >
              > > > > > >
              > > > > >
              > > > >
              > > > >
              > > > >
              > > > >
              > > > >
              > > > > Yahoo! Groups Links
              > > > >
              > > > >
              > > > >
              > > > >
              > > >
              > > >
              > > >
              > >
              >
              >
              >
              > Yahoo! Groups Links
              >
              >
              >
              >
              >
            Your message has been successfully submitted and would be delivered to recipients shortly.