25

In my Rails 3 application I do:

render :js => "alert(\"Error!\\nEmpty message sent.\");" if ...

Sometimes, below this error message (in the same alert box) I see: "Prevent this page from creating additional dialogs" and a checkbox.

What does this mean ?

Is that possible not to display this additional text and checkbox ?

I use Firefox 4.

Misha Moroshko
  • 166,356
  • 226
  • 505
  • 746

6 Answers6

27

It's a browser feature to stop websites that show annoying alert boxes over and over again.

As a web developer, you can't disable it.

Marcel Korpel
  • 21,536
  • 6
  • 60
  • 80
10

What does this mean ?

This is a security measure on the browser's end to prevent a page from freezing the browser (or the current page) by showing modal (alert / confirm) messages in an infinite loop. See e.g. here for Firefox.

You can not turn this off. The only way around it is to use custom dialogs like JQuery UI's dialogs.

Pekka
  • 442,112
  • 142
  • 972
  • 1,088
  • 4
    Just to add: from Firefox 4 onwards those alerts are not modal anymore, at least not to the window manager. You can easily navigate away to other tabs/windows nowadays. – Marcel Korpel May 01 '11 at 12:41
3

You can create a custom alert box using java script, below code will override default alert function

window.alert = function(message) { $(document.createElement('div'))
    .attr({
      title: 'Alert',
      'class': 'alert'
    })
    .html(message)
    .dialog({
      buttons: {
        OK: function() {
          $(this).dialog('close');
        }
      },
      close: function() {
        $(this).remove();
      },
      modal: true,
      resizable: false,
      width: 'auto'
    });
};
whoan
  • 8,143
  • 4
  • 39
  • 48
Arun
  • 41
  • 4
  • Can you show how to use this? Maybe add a little description of how to use and whats happening? – drooh Jan 29 '16 at 17:22
0

I designed this function to hopefully circumvent the checkbox in my web apps.

It blocks all functionality on the page while executing (assuming fewer than three seconds has passed since the user closed the last dialog), but I prefer it to a recursive or setTimeout function since I don't have to code for the possibility of something else being clicked or triggered while waiting for the dialog to appear.

I require it most when displaying errors/prompts/confirms on reports that are already contained within Modalbox. I could add a div for additional dialogs, but that just seems too messy and unnecessary if built-in dialogs can be used.

Note that this would probably break if dom.successive_dialog_time_limit is changed to a value greater than 3, nor do I know if Chrome has the the same default as Firefox. But at least it's an option.

Also, if anyone can improve upon it, please do!

// note that these should not be in the global namespace
var dlgRslt,
    lastTimeDialogClosed = 0;

function dialog(msg) {
    var defaultValue,
        lenIsThree,
        type;

    while (lastTimeDialogClosed && new Date() - lastTimeDialogClosed < 3001) {
        // timer
    }

    lenIsThree = 3 === arguments.length;
    type = lenIsThree ? arguments[2] : (arguments[1] || alert);
    defaultValue = lenIsThree && type === prompt ? arguments[1] : '';

    // store result of confirm() or prompt()
    dlgRslt = type(msg, defaultValue);
    lastTimeDialogClosed = new Date();
}

usage: 

dialog('This is an alert.');

dialog( 'This is a prompt', prompt );
dialog('You entered ' + dlgRslt);

dialog( 'Is this a prompt?', 'maybe', prompt );
dialog('You entered ' + dlgRslt);

dialog( 'OK/Cancel?', confirm );
if (dlgRslt) {
    // code if true
}
Queue
  • 408
  • 5
  • 7
0

This is a browser feature.

If you could, try to employ http://bootboxjs.com/, whit this library you can do the same of 

alert("Empty message sent");

by writing:

bootbox.alert("Empty message sent", function(result) {
    // do something whit result
 });

You'll get a nice user interface too!

zeppaman
  • 844
  • 8
  • 23
0

Using JQuery UI's dialogs is not always a solution. As far as I know alert and confirm is the only way to stop the execution of a script at a certain point. As a workaround we can provide a mechanism to let the user know that an application needs to call alert and confirm. This can be done like this for example (where showError uses a jQuery dialog or some other means to communicate with the user):

var f_confirm;
function setConfirm() {
  f_confirm = confirm;
  confirm = function(s) {
    try {
      return f_confirm(s);
    } catch(e) {
      showError("Please do not check 'Prevent this page from creating additional dialogs'");
    }
    return false;
  };
};
mozey
  • 2,222
  • 2
  • 27
  • 34
  • 2
    "alert and confirm is the only way to stop the execution of a script at a certain point" - When you're thinking synchronously, that's true. However, these can use the jQueryUI controls to fire another method that then handles the result. – GalacticCowboy Feb 03 '12 at 17:22
  • It is true when you're thinking asynchronously as well. Using callbacks does not stop code executing in between. But as you say, passing in a callback function is a great way to control flow when using the jQuery dialogs. – mozey Apr 09 '12 at 14:57