This project is archived and is in readonly mode.

#128 ✓invalid
3n

proccessScripts error with BOM in IE

Reported by 3n | June 14th, 2008 @ 12:39 AM | in 2.0 (closed)

On both 1.2b2 and 1.2 there is an error within the processScripts method where the text argument being null causes an error.

If you do an early return when 'text' is not defined all is well.

Comments and changes to this ticket

  • Jan Kassens

    Jan Kassens July 19th, 2008 @ 12:14 PM

    • Assigned user changed from “Valerio” to “Jan Kassens”
    • Tag set to 1.2b2, 1.2release, defect, iphone, trivial
  • Jan Kassens

    Jan Kassens July 26th, 2008 @ 09:07 AM

    • State changed from “new” to “invalid”
    • Tag changed from 1.2b2, 1.2release, defect, iphone, trivial to 1.2, defect, iphone

    a demo / example code is needed in this case.

  • Kai Gülzau

    Kai Gülzau February 22nd, 2010 @ 12:25 PM

    • Tag changed from 1.2, defect, iphone to defect, iphone

    I had the same problem with an IIS6 which always prefixes the response with 3 Bytes.
    If these bytes are sent by the server IE does have an undefined/null xhr.responseText.

    Example/Demo: http://mootools.net/shell/n8L2L/

    Request.processScripts has to be patched:

    processScripts: function(text){
      if ($defined(text)) {
      ...
      }
    }
    
  • Kai Gülzau

    Kai Gülzau February 22nd, 2010 @ 01:55 PM

    • Title changed from “proccessScripts error on iPhone” to “proccessScripts error with BOM in IE”

    IIS does send a BOM http://en.wikipedia.org/wiki/Byte_Order_Mark in the response.
    UTF-8: EF BB BF

    Does anybody know how to disbale the BOM in IIS?

    Should i open a new ticket?

Create your profile

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

Shared Ticket Bins

People watching this ticket

Tags

Referenced by

Pages