This project is archived and is in readonly mode.

#75 ✓invalid
surfer

Ajax and Entities

Reported by surfer | May 30th, 2008 @ 11:49 AM | in 2.0 (closed)

After trying various setups I can only conclude that there must be a bug with trunk 1555.

See link for more information.

http://forum.mootools.net/viewto...

Comments and changes to this ticket

  • Valerio

    Valerio May 31st, 2008 @ 07:57 AM

    • State changed from “new” to “hold”

    Cant help you without a testcase.

  • surfer

    surfer May 31st, 2008 @ 11:15 AM

    digitarald clarified that XHTML does not support entities by default. I was under the impression that XHTML was able to use HTML entities.

    Which leads me to another question. What exactly changed from 1.1/1.2b2 to the latest trunk with regards to the request class? It's seems to be XHTML strict now, where as before I never got errors which was beneficial for old database content.

  • surfer

    surfer May 31st, 2008 @ 12:36 PM

    Another issue that the latest trunk gives me is the impossibility to include embed tags from video sites. I know that embed is depreciated but its almost impossible to write a generic script that can rewrite all the embed/object tags out there to XHTML compliant code. Firefox will display embed tags even though it gives an error, while Safari refuses to parse the response text if it has embed tags.

    As this worked very will with older versions of the request class (1.2b2) I think it would be better to allow the request class to be a little more permissive.

  • surfer

    surfer May 31st, 2008 @ 01:17 PM

    I found what differed between the two versions.

    I used the "update" option that updates an element with the responseText. This gave no errors in 1.2b2. By using the onComplete and setting the innerHtml with responseHTML I got it working with the latest trunk.

  • digitarald

    digitarald June 3rd, 2008 @ 08:15 AM

    Moving the update option to the Request class would solve it. Its also reasonable, since the script-tag-handling is also in the class Request (so it already has HTML-processing functionality). Request.HTML would be only for advanced HTML requests, not the simple Ajax updates. All the XML processing is overload for such simple tasks, but good for advanced stuff.

    surfer: For which browser do you wrap objects and embeds? The Swiff class works without it. The class can't be less permissive, the validation comes automatically with the XML-Parser. Maybe it could fallback silently on parsing-errors.

  • surfer

    surfer June 2nd, 2008 @ 01:19 PM

    Thanks for your reply digitarald.

    Have I understood it correctly that when using update with the latest trunk the response is handled as XML?

    My situation is that I am developing a blog and I want to be able to give my users the ability of adding flash video to their entries. As we all now, the embed code found on most sites is not strict HTML or XHTML. To make it compliant with XHTML I would need to write a script that can parse all embed code's and rewrite to an object tag.

  • UloPe

    UloPe August 28th, 2008 @ 02:01 PM

    • Tag set to core, minor, request

    #182 also concerns this

  • UloPe

    UloPe August 28th, 2008 @ 02:02 PM

    • Tag cleared.

    sorry no idea why it changed the tags

  • Christoph Pojer

    Christoph Pojer November 9th, 2010 @ 06:59 PM

    • State changed from “hold” to “invalid”
    • Milestone order changed from “0” to “0”

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

Referenced by

Pages