Problems with AOL/CS browsers

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Joshua Beall

    Problems with AOL/CS browsers

    Hi All,

    I have run up against a strange error that seems affect only older version
    of AOL and CS browsers (AOL earlier than vs 8.0, and not sure what versions
    of CS): when I have a form, and set the target="_blank" , when the user
    clicks on that button, he gets sent to the action page, but no form data is
    submitted with the request! $_POST is completely empty!

    Has anyone else ever encountered this behavior? Is there a workaround?
    What versions of AOL/CS does it affect?

    Any help on this matter would be appreciated!

    -Josh


  • Michael Vilain

    #2
    Re: Problems with AOL/CS browsers

    In article <RIyXb.6453$wD5 .1676@nwrddc03. gnilink.net>,
    "Joshua Beall" <jbeall@donotsp am.remove.me.he raldic.us> wrote:
    [color=blue]
    > Hi All,
    >
    > I have run up against a strange error that seems affect only older version
    > of AOL and CS browsers (AOL earlier than vs 8.0, and not sure what versions
    > of CS): when I have a form, and set the target="_blank" , when the user
    > clicks on that button, he gets sent to the action page, but no form data is
    > submitted with the request! $_POST is completely empty!
    >
    > Has anyone else ever encountered this behavior? Is there a workaround?
    > What versions of AOL/CS does it affect?
    >
    > Any help on this matter would be appreciated![/color]

    I would imagine the work-around to be to code the page to not support
    that browser or use the GET method.

    --
    DeeDee, don't press that button! DeeDee! NO! Dee...



    Comment

    • Ike

      #3
      Re: Problems with AOL/CS browsers

      Doesn't _blank mean to open a new instantiation of the browswer? If so,
      check to make sure tehre is not some kind of popup stopper mugging you. -Ike

      "Joshua Beall" <jbeall@donotsp am.remove.me.he raldic.us> wrote in message
      news:RIyXb.6453 $wD5.1676@nwrdd c03.gnilink.net ...[color=blue]
      > Hi All,
      >
      > I have run up against a strange error that seems affect only older version
      > of AOL and CS browsers (AOL earlier than vs 8.0, and not sure what[/color]
      versions[color=blue]
      > of CS): when I have a form, and set the target="_blank" , when the user
      > clicks on that button, he gets sent to the action page, but no form data[/color]
      is[color=blue]
      > submitted with the request! $_POST is completely empty!
      >
      > Has anyone else ever encountered this behavior? Is there a workaround?
      > What versions of AOL/CS does it affect?
      >
      > Any help on this matter would be appreciated!
      >
      > -Josh
      >
      >[/color]


      Comment

      • Joshua Beall

        #4
        Re: Problems with AOL/CS browsers

        "Ike" <rxv@hotmail.co m> wrote in message
        news:zAzXb.5589 $hm4.2293@newsr ead3.news.atl.e arthlink.net...[color=blue]
        > Doesn't _blank mean to open a new instantiation of the browswer? If so,
        > check to make sure tehre is not some kind of popup stopper mugging[/color]
        you. -Ike

        _blank does indeed mean "open new browser". But it is not a blocked popup
        problem, because they do get sent to that page - it is just that there is no
        POST data that gets sent along with the request.

        Unless somehow the popup blocker were to allow the popup, but cleaned the
        HTTP request of any of the POST data? Seems like a strange thing...

        -jb


        Comment

        • Joshua Beall

          #5
          Re: Problems with AOL/CS browsers

          <Michael Vilain <vilain@spamcop .net>> wrote in message
          news:vilain-89A210.16164714 022004@comcast. ash.giganews.co m...[color=blue]
          > In article <RIyXb.6453$wD5 .1676@nwrddc03. gnilink.net>,
          > "Joshua Beall" <jbeall@donotsp am.remove.me.he raldic.us> wrote:
          > I would imagine the work-around to be to code the page to not support
          > that browser or use the GET method.[/color]

          Yeah, I kinda thought so, and I am actually in the process of converting
          that portion of the script to a GET call.

          What I really wanted to know is if anybody else had experience this
          behavior, so I could more accurately identify just what browsers do this.
          Right now I only have a vague idea that it is older versions of AOL and CS
          browsers.

          -jb


          Comment

          Working...