Hopefully core team can sort out a bugfix release for 1.7 that updates
to a newer sizzlejs, solving this problem.. Have posted in Prototype
Core, but awaiting moderation..
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to
Great, have switched out that sizzlejs chunk, and all is good. Was
gonna just switch back to 1.6.0 for the project concerned, but I'm
using Element.Storage, so boo :(
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this
So, any news on Prototype 1.7.0.1, 1.7.1 or 1.8? Assuming it'll have
the latest sizzlejs included?
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com.
To u
Thanks Mr Crowder! You the man, as always..
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com.
To unsubscribe from this group, send email to
prototype-sc
Aha, Mr Crowder, you always have the answers! Thanks.
So, any news on Prototype v 1.7.0.1, 1.7.1 or 1.8? Will the next
version have the latest Sizzle in?
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send
I *think* this is exactly what html5shiv is doing. Could try adding
your suggestion into the test HTML on pastebin, but I'm not at my
computer right now :(
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, sen
Using html5shiv 1.6.2 (latest) (http://code.google.com/p/html5shiv/)
and Prototype v1.7..
So, html5shiv makes , etc elements work nicely in
IE<9 .. they appear, you can style them etc. All good. The HTML5
elements all exist within the IE DOM tree in Developer Tools.
However, when you try to grab
So, here's the picture as far as I can tell..
The only way to send multi-byte utf8 characters in their raw form
without them being urlencoded is to use a POST with Content-Type
'multipart/form-data'.
Common browser behaviour for POSTing forms with this Content-Type (in
a non-AJAX context) is to s
as a bonus, in the case of my problem, I don't even need to tag
requests with a uniqid or serial, as I know that I'm only interested
in responses to requests where the search string was the same as the
current form field value.
On Mar 20, 9:26 am, Szymon Wilkołazki wrote:
>
> The better approach
I've now found a solution to this problem, as follows:
var inputControlCapturedValue = inputControl.getValue();
new Ajax.Request(xhrRequestUrl, {
method: 'get',
parameters: {
table: s_
Thanks for that link Alex.
However, as I've tried to proceed with this, I keep coming back to
needing answers to my two original questions. Can anyone assist?
The questions:
- Which callback will allow me to intercept Ajax.updater at this
point? Will this even work with Ajax.updater, or do I ne
I use the following Ajax.Updater code to auto-complete (refresh) the
options within a select box according to text entered into an input
[type=text].
The code is part of a function which is envoke by the 'onkeyup' event
on the input:
new Ajax.Updater(targetSelect.identify(), xhrRequestUrl, {
12 matches
Mail list logo
