Hi,
I didn't find the other way to report bugs in prototype.js
It's described here:
http://prototypejs.org/contribute
i am quite sure it was supposed to be:
if (!responders) return element;
Indeed. Well-spotted!
--
T.J. Crowder
tj / crowder software / com
www.crowdersoftware.com
On
https://prototype.lighthouseapp.com/projects/8886-prototype/tickets/810-fix-eventstopobserving-to-return-element
On 25 сен, 19:17, T.J. Crowder t...@crowdersoftware.com wrote:
Hi,
I didn't find the other way to report bugs in prototype.js
It's described
You are surely right about the utility of Number object over
primitives and the overhead it can be. I use the Number Constructor to
parse string and convert to Number and store it like that in my cache.
In the cache, there are other custom objects that inherits from
Number.
Cordially,
Alex
On 8
there are other custom objects that inherits from Number.
And that works cross-browser !?
Best,
Tobie
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to
I just want to be compatible with Firefox or Webkit. I don't use IE :)
On 9 oct, 10:18, Tobie Langel [EMAIL PROTECTED] wrote:
there are other custom objects that inherits from Number.
And that works cross-browser !?
Best,
Tobie
--~--~-~--~~~---~--~~
You
On Oct 9, 4:11 am, atrepp [EMAIL PROTECTED] wrote:
You are surely right about the utility of Number object over
primitives and the overhead it can be. I use the Number Constructor to
parse string and convert to Number and store it like that in my cache.
Why don't you use `Number` (as a
I learnt something, i didn't know that you can use Number as a
function, i think i will move to primitives.
thanks,
Alex :)
On 9 oct, 15:40, kangax [EMAIL PROTECTED] wrote:
On Oct 9, 4:11 am, atrepp [EMAIL PROTECTED] wrote:
You are surely right about the utility of Number object over
I have a DB Cache where i store the value in Number object, i want to
send back this value without to use valueOf each time.
And Hash.toQueryString() is a good example why it should detect Number
Object. I don't think that this function can ignore Number Object.
Cordially,
Alex
On 7 oct, 17:05,
POLS is a no-brainer here. Since this IS a legit line in javascript:
var n = new Number(4);
then saying:
Object.isNumber(n); = false
is ridiculous. Regardless of whether using new Number is preferred syntax
or not, its craziness to claim that that's a valid response for that
function.
-Jerod
why go throw all this complexity when javascript has a native isNaN function...
On Wed, Oct 8, 2008 at 6:40 PM, Tom Gregory [EMAIL PROTECTED] wrote:
Thanks for the reply.
I realize I don't get a vote here, but IMHO it either needs to be a)
well documented that Object.isNumber( new
I shall end the shitstorm here and now.
To quote the rhino book:
Once we've created a string object S [through `new String`], what can
we do with it? Nothing that we cannot do with the corresponding
primitive string value. If we use the `typeof` operator, it tells us
that S is indeed an object,
On Oct 8, 2008, at 11:29 AM, Andrew Dupont wrote:
I shall end the shitstorm here and now.
... he probably can't think of a single case in which it's
_useful_ to use the wrapper objects instead of the primitives they
wrap.
Honestly, I can't either. I don't see any reason to use the
No, you were completely right — either it should support both the
primitive and the wrapper _or_ we need to document why it does not. I
was prepared to say we'd do the latter, since I didn't want to deal
with the differences between the two, but it turns out there _are_ no
differences, save for
On Oct 7, 5:21 am, atrepp [EMAIL PROTECTED] wrote:
Hi,
I have a problem with Object.isNumber() because it test only for type
number and not for the object Number.
http://prototype.lighthouseapp.com/projects/8886-prototype/tickets/37...
With Webkit (5525.20.1) and Protototype 1.6.0.3 :
Sorry It is not :
if (Object.isNumber(values))
return results.push(toQueryPair(key, values.toString()));
but
if (Object.isNumber(values))
results.push(toQueryPair(key, values.toString()));
On 7 oct, 11:21, atrepp [EMAIL PROTECTED] wrote:
Bug 2
On Oct 7, 11:17 am, Tom Gregory [EMAIL PROTECTED] wrote:
How 'bout POLS?
It's a bit hard to tell what intuitive definition of number is in
a weakly typed language. According to ECMA-262 specs, an object
created with `new Number` is not of type number but rather of type
object. Besides somewhat
We don't know if you're doing something wrong because you haven't told or
shown us what you are doing. But, the code you are referring to is pretty
internal to event handling, so I don't think you might be doing something
wrong.
What we need from you if full code where this happens (use
That's a lot of code to dig through. Couldn't you just save the result HTML
document from the browser instead of pasting all the sources?
We are interested only in JavaScript code and HTML that it applies to.
On Dec 4, 2007 3:48 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
P.S.: (
Archive cliente_upd.php :
?
include(inc/lib.inc.php);
#define de ACAO
define(NG_ACAO, CLI_DETAIL);
#verifica_permissao
checkPermission();
$page = new Smarty();
$cl = new clientes();
$cl-NR_CLIENTE = $_GET[nr];
$cl-load();
if(empty($cl-NOME)) {
$page-assign(not_updated, true);
I took some time to actually read the last bits of the code. First of all,
you didn't paste us masks.js, which is pretty important for this case. But,
you don't have to because the source of your problems is not Prototype
framework, but the fact you are trying to observe events by passing NULL
1) Get the current versio of Prototype. You're not using 1.6.0 final.
2) The below means you're trying to observe an event on a non-existing
element (your setupOneElementMask function calls observe on null.
Please direct usage questions to the rails-spinoffs google group.
This group is for
Thanx xinze,
In the readme_first.txt file I point out that I had implemented some
patches from various tickets.
I goofed the patch on that one.
http://dev.rubyonrails.org/ticket/8843
should have been:
results.push($(query.snapshotItem(i)));
I will fix this bug and release a new package when
Okay, I have assigned a ticked for this:
http://dev.rubyonrails.org/ticket/9824
Hope that helps even more
Luke
On Oct 8, 10:00 pm, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
hey there, thanks for responding so promptly :)
Tobie, I have tried to use t.getHeader('Content-type'); but returns
On 10/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I know konqueror is probably insignificant to most people, but I want
to ensure my project works for everything recent. So could this please
be addressed :)
Thanks for reporting. Konqueror, although not officially supported, is of
Hi Luke,
Thanks for the info.
Mind opening a bug report for it ? That would be really helpful.
Have you run the test suite on Konqueror, any ajax related tests
failing ?
I'm suspecting it might be an issue with the content headers, could
you please let me know what you get for the following:
I figured the issue out.
if (Prototype.BrowserFeatures.XPath) {
document._getElementsByXPath = function(expression, parentElement) {
var results = [];
var query = document.evaluate(expression, $(parentElement) ||
document,
null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);
Guys,
the code document.write(script id=__onDOMContentLoaded defer
src=//:\/script);
is for IE mainly and anything else that falls into that category. No
need to work for the others.
The reason he uses '//:' its a trick that works for both HTTPS and
HTTP. Its less code than doing all
I forgot to mention that without that little trick on an HTTPS site in
IE you get an ugly warning dialog...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email
This technique is also used in Extjs.
It covers most cases, sure. However, it potentially fails in situations
where resource lazy loading is used heavily. In our widget framework, each
widget is responsible for encapsulating its own resource requirements, so it
sometimes possible to have code
Using FF and/or the patch previously mentioned and no requests are made.
On 22/08/07, Mislav Marohnić [EMAIL PROTECTED] wrote:
On 8/22/07, Wiktor Ihárosi [EMAIL PROTECTED] wrote:
I think Sam had reason to write this. I reread Dean Edwards's - who
else? :) - post about the window.onload and
On 23/08/07, Mislav Marohnić [EMAIL PROTECTED] wrote:
On 8/23/07, Richard Quadling [EMAIL PROTECTED] wrote:
Using FF and/or the patch previously mentioned and no requests are made.
Can you please try
src=//:
... like in Base2 and see if there are requests. Thanks
Being a numpty, my
On 8/23/07, Richard Quadling [EMAIL PROTECTED] wrote:
This needs to become what? I don't know what Base2 is (sorry).
document.write(script id=__onDOMContentLoaded defer src=//:\/script);
--~--~-~--~~~---~--~~
You received this message because you are
On 23/08/07, Mislav Marohnić [EMAIL PROTECTED] wrote:
On 8/23/07, Richard Quadling [EMAIL PROTECTED] wrote:
This needs to become what? I don't know what Base2 is (sorry).
document.write(script id=__onDOMContentLoaded defer src=//:\/script);
Works fine in IE7 and FF using 1.6.0_rc0. No
On Aug 23, 11:35 am, Richard Quadling [EMAIL PROTECTED]
wrote:
document.write(script id=__onDOMContentLoaded defer src=//:\/script);
Works fine in IE7 and FF using 1.6.0_rc0. No requests made.
Great! :)
ps: I obviously meant //: when I wrote ://. sorry for the typo...
On 23/08/07, Wiktor Ihárosi [EMAIL PROTECTED] wrote:
On Aug 23, 11:35 am, Richard Quadling [EMAIL PROTECTED]
wrote:
document.write(script id=__onDOMContentLoaded defer
src=//:\/script);
Works fine in IE7 and FF using 1.6.0_rc0. No requests made.
Great! :)
ps: I obviously meant //:
On Aug 23, 2:03 pm, Richard Quadling [EMAIL PROTECTED]
wrote:
That's now generating requests.
I think I was not clear enough. The correct and working syntax is //:
which Mislav mentioned. In my first letter I made a typo, but Mislav
wrote the correct syntax for you. He is right,
On 23/08/07, Wiktor Ihárosi [EMAIL PROTECTED] wrote:
On Aug 23, 2:03 pm, Richard Quadling [EMAIL PROTECTED]
wrote:
That's now generating requests.
I think I was not clear enough. The correct and working syntax is //:
which Mislav mentioned. In my first letter I made a typo, but Mislav
I'm not sure why Sam put it in there. The correct form should be:
var src = javascript:void(0);
if (location.protocol == https:) src = https://; + src;
document.write(script id=__onDOMContentLoaded defer src=' + src +
'\/script);
Sam, can you replace this?
On 8/22/07, [EMAIL
On 8/22/07, Wiktor Ihárosi [EMAIL PROTECTED] wrote:
I think Sam had reason to write this. I reread Dean Edwards's - who
else? :) - post about the window.onload and one of the last comment
says with https you can remove the protocol.
Done:
http://dev.rubyonrails.org/ticket/8951
On 7/11/07, jdalton [EMAIL PROTECTED] wrote:
On Snap!
Tricky, they define it again for WebKit and IE.
Follow the info here :
http://www.prototypejs.org/contribute
and create a ticket 8)
You can post back here with a link to the ticket if you
I modified a similar ticket dealing with code in the same area:
http://dev.rubyonrails.org/ticket/8851
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to
prototype-1.5.1.1:
line 406:
unescapeHTML: function() {
return this.replace(/amp;/g,'').replace(/lt;/g,'').replace(/gt;/g,'');
}
but should be
unescapeHTML: function() {
return this.replace(/lt;/g,'').replace(/gt;/g,'').replace(/amp;/g,'');
}
Compare the results of
var
On Snap!
Tricky, they define it again for WebKit and IE.
Follow the info here :
http://www.prototypejs.org/contribute
and create a ticket 8)
You can post back here with a link to the ticket if you wish.
--~--~-~--~~~---~--~~
You received this message because
Tom Gregory a écrit :
1) Does this solution continue to work when borders are assigned with
element/class selectors, rather than inline?
Probably not, as the style property does not always contain computed
styles, as Thomas will gladly tell you (and as Scripty's code is ample
proof of).
2)
On 4/25/07, Michael Peters [EMAIL PROTECTED] wrote:
This has been fixed in 1.5.1rc3.
Yeah, I've spent days to ensure there's no more breakage in query-related
stuff. Jdalton, please try RC3 and report back if you still think there are
bugs.
Hiya Mislav,
I tested in a Prototype 1.5.1rc3 sandbox and the issue appears to be
fixed now.
Thanx
Rock!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to
Two comments--
I should know better than to try to do this quickly without double
checking, but here goes...
1) Does this solution continue to work when borders are assigned with
element/class selectors, rather than inline?
2) I seem to recall there is something screwy with how borders are
On 3/4/07, Thomas Fuchs [EMAIL PROTECTED] wrote:
Next time, please see:
http://prototypejs.org/contribute
Psst! He can't be bothered :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To
48 matches
Mail list logo
