Databases
StackOverflow2013
Postsdbo
PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
    primarykey
    data
    text
    <p>Following Michael Hartl's tutorial. Using Rails 3.0.9 under Ubuntu. The following header is in application.html.erb:</p> <pre><code>&lt;head&gt; &lt;title&gt;&lt;%= title %&gt;&lt;/title&gt; &lt;%= csrf_meta_tag %&gt; &lt;%= render 'layouts/stylesheets' %&gt; &lt;%= javascript_include_tag :defaults %&gt; &lt;/head&gt; </code></pre> <p>No jQuery. Tutorial <a href="http://ruby.railstutorial.org/chapters/updating-showing-and-deleting-users#code%3adelete_links" rel="nofollow">Listing 10.38</a> specifies the Delete action be called as follows:</p> <pre><code>&lt;%= link_to "delete", user, :method =&gt; :delete, :confirm =&gt; "You sure?", :title =&gt; "Delete #{user.name}" %&gt; </code></pre> <p>Here is an example of the generated HTML:</p> <pre><code>&lt;a href="/users/13" data-confirm="You sure?" data-method="delete" rel="nofollow" title="Delete Mylene Gaylord"&gt;delete&lt;/a&gt; </code></pre> <p>I've tested the confirmation under three browsers:</p> <ul> <li>Firefox 3 under Ubuntu: "OK" deletes user, "Cancel" does not (good)</li> <li>Firefox 5 under Win7: "OK" deletes user, "Cancel" does not (good)</li> <li>IE8 under Win7: both "OK" and "Cancel" delete user (bad!)</li> </ul> <p>When using IE8, why is Cancel calling the Delete code, and how do I fix it? Is there a way to test that Cancel does, in fact, cancel the action, no matter what browser is used?</p> <p>Update 9/29/2011: after upgrading to Rails 3.1 and converting from Prototype to jQuery (Tutorial section <a href="http://ruby.railstutorial.org/chapters/rails-3-1#sec%3aprototype_to_jquery" rel="nofollow">13.1.4</a>), IE8 behaves properly: pressing Cancel aborts the delete action. However that doesn't answer the original question of why IE8 can't Cancel the delete from Rails 3.0.9 with Prototype.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWill
    1. USMark Berry
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
      1. USZabba
      1. VTFavorite
    1. COIt seems that there's a similar question about the same subject in http://stackoverflow.com/questions/3772450/rails-3-method-delete-doesnt-work-in-internet-explorer
      singulars
      1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
      1. USAndreDurao
    2. COThanks @AndreDurao. I saw that but I think this is different. I'm not using jQuery, I'm using a later version of Rails, and I _do_ get the popups; it's just that in IE8, the Cancel button doesn't cancel the action.
      singulars
      1. PORails 3 Confirm Delete - in IE8, pressing Cancel still deletes
      1. USMark Berry
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload