Note that there are some explanatory texts on larger screens.

plurals
  1. USjames
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COOk, I finally have figured out my issue here! Success was definitely returned correctly in all browsers. After setting a javascript alert for each of the statuses, I saw that the screen flickered just before the success alert. Then, when I clicked "ok", it flickered again. The issue was that dojo was also re-rendering the screen by converting normal html elements into its dojo components. All that was needed was to surround my check for status==success by a dojo.addOnLoad function call. Now, all browsers handle this properly! Thanks for all the help on here.
      singulars
    2. COI have had some issues with this "success" state in my onevent javascript function. It seems that every browser other than IE has no issue, and re-renders the component after it returns a success state. IE though re-renders AFTER the success state is returned. This is definitely a problem if you're trying to manipulate something in the re-rendered component from your javascript. Every other browser works great though...I have yet to see a work-around for this IE issue.
      singulars
    3. COOk, it is definitely not related to dojo in any way. I did a test and ran the same javascript code on an onclick event, without ajax. (of course took out the if data.status=="success") and I put alerts inside my code to show that the datatable is not being seen when IE is re-rendering the table after an ajax call, but IS seeing the datatable elements when there's no ajax call.
      singulars
 

Querying!

 
Guidance

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