Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Ajax - IE vs FF

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Ajax - IE vs FF

    I have added a couple ajax callback pages to my site.

    They function perfectly in Firefox & Safari (Mac), but not in Internet Explorer 7.

    Has anyone else come across this issue?

    Thanks much.

    Alex Steinman
    Tags: None
    #2
    Re: Ajax - IE vs FF

    I haven't had that problem. If the site is public, share the URL. It may well be your local IE settings for javascript.
    Steve Wood
    See my profile on IADN

    Comment

      #3
      Re: Ajax - IE vs FF

      Thanks for the response, Steve.

      I tried to publish just a sample page along with the callback page without requiring login, but they aren't functioning the same as when a user is logged in.

      I'm fairly certain it isn't an IE security setting, because I've tried lowering the security to the lowest level possible. And I've tried on multiple PCs, versions of IE and in different environments.

      The callback emits a blank response.

      I read in some places that there is a cache issue with IE that affects AJAX, but I don't understand it well enough to know whether this is my issue.

      Here's an example of a site where I read about the IE / AJAX issue:
      http://devcentral.f5.com/weblogs/mac...6/26/3397.aspx

      Thanks for any other thoughts.

      Alex

      Comment

        #4
        Re: Ajax - IE vs FF

        Turn off security at the server to test. Your callback page is a normal A5W page so security has to be set, or at least set to Always Allow. If yiour callback uses some variable that only exists when the user is logged in, that may explain also. You can also test your callback page by just entering the full URL to the page and see if the page creates an error. That is, run the page in the browser.
        Steve Wood
        See my profile on IADN

        Comment

          #5
          Re: Ajax - IE vs FF

          This is a component w/ AJAX I built for Alex for some demo purposes. It's pretty clear it works in Firefox, but not IE. I don't see the solution.

          Here's the link:

          http://test.workings.com/Student_conduct_reports.a5w

          I won't bother ya'll with the complete callback page code, but here's the most pertinent piece:

          Code:
          myResponse = "$('dlg_VSTUDENT').innerHTML = '" + jsEscape(OptionString) + "';"
?myResponse
          with OptionString, of course, being our variable.
          -Steve
          sigpic

          Comment

            #6
            Re: Ajax - IE vs FF

            Steve -

            Can you post the code for the source and callback pages?

            Just a thought - What happens in IE if you remove the code:

            onchange=""

            from the line:

            <select size="1" class="OsxSelect" name="VSTUDENT" id=dlg_VSTUDENT" onchange="">

            ?

            Comment

              #7
              Re: Ajax - IE vs FF

              Actually, I think it might be the SIZE="1" property in the SELECT tag. Can you remove the string

              SIZE="1"

              and retest?

              Comment

                #8
                Re: Ajax - IE vs FF

                Taking the Size="1" out didn't make any difference. For the moment, I'll leave it up without the Size="1".

                Jerry sent me some info about another approach - I'm going to try to get to that today; maybe we can all learn something else/more.
                -Steve
                sigpic

                Comment

                  #9
                  Re: Ajax - IE vs FF

                  A workaround is to put the SELECT tags in the callback page and take them out of the source html page.

                  So if dlg_VSTUDENT_Container is a DIV or TD tag then something like this:

                  myResponse = jsEscape(OptionString)
                  myResponse = "<select class=\"OsxSelect\" name=\"VSTUDENT\" id=\"dlg_VSTUDENT\" >" + myResponse + "</select>"
                  ? "$('dlg_VSTUDENT_Container').innerHTML = '" + JSStringEncode(myresponse) + "';"

                  I used code from the Alpha sample file AJAX_CascadingDropDowns_DBF.AJAX.A5W to test this. When I ran the code with the SELECT tags in the callback page it worked. When I moved the SELECT tags to the SOURCE page I got the same problem in IE that is at issue here - nothing in the SELECT list.

                  Comment

                    #10
                    Re: Ajax - IE vs FF

                    Jeff, you're very much on track. Between your stuff, a pointer from Jerry Brightbill, and an upgrade to my server version, got it working.

                    At its base, IE doesn't like the option select innerHTML to be replaced.

                    Instead I used the A5.form.populateSelect() function for the callback page.

                    Here's some helpful info for future users:

                    A5.form.populateSelect(curID,curValue,clearOld,popList)

                    � �CurID� � This is the ID attribute of the select control
                    � �curValue� � this is the value to show as selected when the control is populated. If it is specified, the control will not show any �blank� or empty option. If it is not specified (value = ��), a blank option will be shown at the bottom of the list of options.
                    � clearOld � this is a True/false input. If true, it clears any values in the select control on the page before creating the new list. If false, it does not clear the list. Normally, this should be �true�
                    � popList � this is the list of values used to create the option list

                    The popList can contain a displayed and separate stored value using

                    Display value|saved value

                    Using your page and the function, you might have something like this
                    Code:
                    ---------
                    optionList = <<%text%
                    Brown, Kevin|0000000027
                    Cox, Alexis|0000000085
                    Demissie, Susanna|0000000052
                    %text%
                    ?"A5.form.populateSelect('dlg_VSTUDENT','',true,'"+js_Escape(optionList)+"');"
                    ---------
                    If you don't want the select to have any blanks, just open on the first value in the list of values.
                    Code:
                    ---------
                    firstval = word(word(optionList,1,crlf()),2,"|")
                    ?"A5.form.populateSelect('dlg_VSTUDENT','"+firstval+"',true,'"+js_Escape(optionList)+"');"

                    An example of this can be found in the Web App Server Demo "AJAX_CascadingDropDowns_DBF" example.
                    Last edited by Steve Workings; 03-18-2009, 08:41 AM.
                    -Steve
                    sigpic

                    Comment

                    Previous template Next
                    Working...
                    X