Results 1 to 2 of 2

Thread: Triggering an Ext.Msg dialog from an Ext.Msg dialog causes a TypeError

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Dec 2013
    Vote Rating

    Default Triggering an Ext.Msg dialog from an Ext.Msg dialog causes a TypeError


    For Sencha Touch it seems that triggering a Ext.Msg dialog from a callback for a Ext.Msg dialog causes a TypeError. Here's a test case:

    Touch version tested:
    • Touch 2.3 rev 1
    Browser versions tested against:
    • Chrome 31.0.1650.63
    DOCTYPE tested against:
    • When a callback from a Ext.Msg dialog triggers another Ext.Msg a TypeError occurs.
    Steps to reproduce the problem:
    • In Sencha Touch, trigger an Ext.Msg.alert or Ext.Msg.prompt dialog
    • Set the dialog's callback to trigger another dialog
    The result that was expected:
    • No TypeError would occur
    The result that occurs instead:
    • A TypeError occurs

  2. #2
    Sencha - Support Team
    Join Date
    Oct 2011
    Vote Rating


    Thanks for the report. I just filed a bug report for this issue today. Jira id TOUCH-5283.
    Get more personalized support via a support subscription.

    Need more help with your app? Hire Sencha Services

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

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