Corey Jewett schrieb:
> Safari crashed for me. :(
>
We had that before. Fortuanetely, with the new and improved *blingbling*
testsuite, it is easier to track down the issue. All we, or rather you,
as jQuerys primary-safari-tester, need is a local webserver (eg. Apache
with PHP installed). And
> Cool - the before hook is working for me - thanks :)
Jörn,
As Dave pointed out, using 'before' actually creates a conflict with
the form plugin. I should not have suggested it. The form plugin
accepts a before handler in its options arg but ultimately passes the
same options arg on to $.ajax.
Jörn Zaefferer wrote:
> Mike Alsup schrieb:
>> preprocess: function(xml) {
>>
>> The form plugin uses 'before' for the preprocess hook. For
>> consistency, maybe using that name would be a good idea.
>>
> Done.
>
> Still, setting custom request headers in IE(5 - 7) fails
Safari crashed for me. :(
IE6 and IE7:
2 failures:
24. core module: not(String) (1, 1, 2)
not('selector')
not('selector, selector') expected: [object],[object],[object],
[object], result: [object],[object],[object],[object],[object]
70. ajax module: $.ajax - preprocess (1, 0, 1)
check return
Safari:
jQuery Test Suite - Core
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418.9.1 (KHTML,
like Gecko) Safari/419.3
core module: Basic requirements (0, 7, 7)
core module: length (0, 1, 1)
core module: size() (0, 1, 1)
core module: get() (0, 1, 1)
core module: get(Number) (0, 1, 1)
c
Corey Jewett schrieb:
> Do you have an isolated test case proving IE is ignoring
> setRequestHeader?
>
It's part of the testsuite, available in SVN. It's a bit complicate to
isolate the problem: I'm not sure what is happening on the serverside
and I can't debug it. I can't even see what is a
Do you have an isolated test case proving IE is ignoring
setRequestHeader?
Corey
On Dec 4, 2006, at 11:47 AM, Jörn Zaefferer wrote:
> Mike Alsup schrieb:
>> preprocess: function(xml) {
>>
>>
>> The form plugin uses 'before' for the preprocess hook. For
>> consistency, maybe using
> The form plugin's call point is earlier and lets you modify the form before
> it's serialized and passed on to ajax(), which would now have a "before"
> handler. If there's some way to resolve the call arguments and "this" usage
> I think it would be great to extend "before", but it seems tricky.
>> $.ajax({
>> ...
>> preprocess: function(xml) {
>>xml.setRequestHeader(...);
>>xml.otherStuff();
>> }
>> });
>
> Exactly my thought! but preprocess is too many bytes! (ha ha )
Let's use "b4" then. :-) Just kidding!
> The form plugin uses 'before' for the preproce
Mike Alsup schrieb:
> preprocess: function(xml) {
>
>
> The form plugin uses 'before' for the preprocess hook. For
> consistency, maybe using that name would be a good idea.
>
Done.
Still, setting custom request headers in IE(5 - 7) fails, anyone got any
clue?
http://j
I was thinking prep, but if the ideas are similar to before in forms,,, I'm
all for it!
On 12/4/06, Mike Alsup <[EMAIL PROTECTED]> wrote:
> >> > preprocess: function(xml) {
The form plugin uses 'before' for the preprocess hook. For
consistency, maybe using that name would be a good idea.
> >> > preprocess: function(xml) {
The form plugin uses 'before' for the preprocess hook. For
consistency, maybe using that name would be a good idea.
Mike
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
>> > preprocess: function(xml) {
> It'd work for me (and Kevin, i suppose) too. +1 for taking that route.
I like that too.
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Exactly my thought! but preprocess is too many bytes! (ha ha )
On 12/4/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Ⓙⓐⓚⓔ schrieb:
> Exactly my point... IE is not part of my solution. I want to support
> setmimetype.. not JQ! I understand JQ is trying to be a base for all
> the stated browsers.
On 12/4/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Ⓙⓐⓚⓔ schrieb:
> > Exactly my point... IE is not part of my solution. I want to support
> > setmimetype.. not JQ! I understand JQ is trying to be a base for all
> > the stated browsers... I just want to extend it.
> I see, good point. How about
Ⓙⓐⓚⓔ schrieb:
> Exactly my point... IE is not part of my solution. I want to support
> setmimetype.. not JQ! I understand JQ is trying to be a base for all
> the stated browsers... I just want to extend it.
I see, good point. How about something like this:
$.ajax({
...
preprocess: functi
Exactly my point... IE is not part of my solution. I want to support
setmimetype.. not JQ! I understand JQ is trying to be a base for all the
stated browsers... I just want to extend it.
On 12/4/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Ⓙⓐⓚⓔ schrieb:
> I think John would rather cut down the
Ⓙⓐⓚⓔ schrieb:
> I think John would rather cut down the size of jq instead of adding
> little features for a few people, which is why I suggest if we had a
> pre-ajax callback where we can massage the req (at about the same
> place as your patch).. we both could be happy and this will probably
>
I think John would rather cut down the size of jq instead of adding little
features for a few people, which is why I suggest if we had a pre-ajax
callback where we can massage the req (at about the same place as your
patch).. we both could be happy and this will probably handle lots of future
requ
Choan C. Gálvez wrote:
> On 12/4/06, Kelvin Luck <[EMAIL PROTECTED]> wrote:
>> So I made the attached little patch (against jquery-1.0.3.js [Rev: 501])
>> which just allows you to pass extra headers to the ajax call. It seems
>> to be working for me - please consider it for inclusion into jQuery,
>
On 12/4/06, Kelvin Luck <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm just working on a project which is making ajax calls to a .NET
> backend using the AjaxPro extension. However, since I'm already using
> jQuery on the front end I thought I'd avoid using their extra frontend
> code and just use jQuery
you want this... I want that... perhaps if we had a pre-ajax callback where
we can massage the req (at about the same place as your patch).. we both
could be happy and this will probably handle lots of future requirements.
I wanted overrideMimeType for files served as text/html but requested as
t
Hi,
I'm just working on a project which is making ajax calls to a .NET
backend using the AjaxPro extension. However, since I'm already using
jQuery on the front end I thought I'd avoid using their extra frontend
code and just use jQuery.
The problem is that their .NET backend expects a custo
23 matches
Mail list logo
