Jump to content

Jquery Post data chrome/safari issue


dflow

Recommended Posts

im receiving the following error from firebug

  Quote

Uncaught Error: "create" can only be used in extension processes. See the content scripts documentation for more details.

chromeHidden.onLoad.addListener.apiDefinitions.forEach.apiDef.functions.forEach.apiFunction

extensions/schema_generated_bindings.js:418

(anonymous function)

 

i have  the following form submit jquery

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
  <script type="text/javascript">
    $(function() {
      $('form#addtocart').submit();
    });
  </script>

this form submits data to paypal sandbox

in firefox it submits the data just fine

any ideas what went wrong?

Link to comment
https://forums.phpfreaks.com/topic/262158-jquery-post-data-chromesafari-issue/
Share on other sites

  Quote

im receiving the following error from firebug

  Quote

Uncaught Error: "create" can only be used in extension processes. See the content scripts documentation for more details.

chromeHidden.onLoad.addListener.apiDefinitions.forEach.apiDef.functions.forEach.apiFunction

extensions/schema_generated_bindings.js:418

(anonymous function)

 

i have  the following form submit jquery

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
  <script type="text/javascript">
    $(function() {
      $('form#addtocart').submit();
    });
  </script>

this form submits data to paypal sandbox

in firefox it submits the data just fine

any ideas what went wrong?

No idea. Any more code you can share? As far as I can tell as soon as your document loads it's submitting a form. Other than that, what else can be determined from what you've supplied?

  Quote

  Quote

im receiving the following error from firebug

  Quote

Uncaught Error: "create" can only be used in extension processes. See the content scripts documentation for more details.

chromeHidden.onLoad.addListener.apiDefinitions.forEach.apiDef.functions.forEach.apiFunction

extensions/schema_generated_bindings.js:418

(anonymous function)

 

i have  the following form submit jquery

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
  <script type="text/javascript">
    $(function() {
      $('form#addtocart').submit();
    });
  </script>

this form submits data to paypal sandbox

in firefox it submits the data just fine

any ideas what went wrong?

No idea. Any more code you can share? As far as I can tell as soon as your document loads it's submitting a form. Other than that, what else can be determined from what you've supplied?

 

i found a solution it was an html issue

http://catontech.com/blog/tag/paypal/

 

strange

  Quote

  Quote

target="paypal"

 

Makes no sense.  I've never seen that in PayPal buttons before.

target="paypal" should just open the link in a new window called paypal.

 

The target attribute in HTML has set values: _blank, _self, _parent, _top, as well as to reference a <frame> within the same document.  "paypal" is not one of them.

 

Chrome must just be insanely picky.  Regardless, target="paypal" is not valid.

  Quote

  Quote

  Quote

target="paypal"

 

Makes no sense.  I've never seen that in PayPal buttons before.

target="paypal" should just open the link in a new window called paypal.

 

The target attribute in HTML has set values: _blank, _self, _parent, _top, as well as to reference a <frame> within the same document.  "paypal" is not one of them.

 

Chrome must just be insanely picky.  Regardless, target="paypal" is not valid.

It is also a field to assign the name of a blank target window. So target="paypal" will open a blank window with target name of paypal. Lets say you were to click another link with target paypal after opening the first one. Instead of opening that second link in a new window it would load in the _blank window created by the first link.

  Quote

  Quote

  Quote

  Quote

target="paypal"

 

Makes no sense.  I've never seen that in PayPal buttons before.

target="paypal" should just open the link in a new window called paypal.

 

The target attribute in HTML has set values: _blank, _self, _parent, _top, as well as to reference a <frame> within the same document.  "paypal" is not one of them.

 

Chrome must just be insanely picky.  Regardless, target="paypal" is not valid.

It is also a field to assign the name of a blank target window. So target="paypal" will open a blank window with target name of paypal. Lets say you were to click another link with target paypal after opening the first one. Instead of opening that second link in a new window it would load in the _blank window created by the first link.

 

target is used to direct content to a frame/window that has already been assigned that specific target name.  It does not assign the new window/page/tab, etc., with the given attribute value (name).

 

There might have been more code that came with that PayPal button that worked in conjunction with the button, for example, a frame/iframe that when the button was clicked, a(n) (i)frame with the name "paypal" would receive data and do something.

 

But without any said (i)frame, Safari must have spazzed out.

  Quote

  Quote

  Quote

  Quote

  Quote

target="paypal"

 

Makes no sense.  I've never seen that in PayPal buttons before.

target="paypal" should just open the link in a new window called paypal.

 

The target attribute in HTML has set values: _blank, _self, _parent, _top, as well as to reference a <frame> within the same document.  "paypal" is not one of them.

 

Chrome must just be insanely picky.  Regardless, target="paypal" is not valid.

It is also a field to assign the name of a blank target window. So target="paypal" will open a blank window with target name of paypal. Lets say you were to click another link with target paypal after opening the first one. Instead of opening that second link in a new window it would load in the _blank window created by the first link.

 

target is used to direct content to a frame/window that has already been assigned that specific target name.  It does not assign the new window/page/tab, etc., with the given attribute value (name).

 

There might have been more code that came with that PayPal button that worked in conjunction with the button, for example, a frame/iframe that when the button was clicked, a(n) (i)frame with the name "paypal" would receive data and do something.

 

But without any said (i)frame, Safari must have spazzed out.

Please test the following code and tell me what happens for you, if you don't believe me.

<a href="http://google.com" target="myframe">Link 1</a><br />
<a href="http://yahoo.com" target="myframe">Link 2</a><br />
<a href="http://bing.com" target="yourframe">Link 3</a><br />
<a href="http://ask.com" target="yourframe">Link 4</a>

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.