pauladaniel / calendardateselect

Automatically exported from code.google.com/p/calendardateselect
Other
0 stars 0 forks source link

Broken under Prototype 1.6.0.2 #98

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Using Firefox 2 or 3
2. Click on the calendar link
3. reports "element.select(expression) has no properties" in prototype.js

What is the expected output? What do you see instead?
I expect to see the calendar, but it does not pop up

What version of the product are you using? On what operating system?
Windows, Linux

Please provide any additional information below.

Original issue reported on code.google.com by bowma...@gmail.com on 26 Mar 2008 at 7:36

GoogleCodeExporter commented 8 years ago
this is the first I've heard of this issue.  Are you sure it's prototype 
1.6.0.2 that's causing the issue?

Original comment by timchar...@gmail.com on 26 Mar 2008 at 8:34

GoogleCodeExporter commented 8 years ago
maybe it similar to issue #95, however it doesnt show such error ..
Ill investigate prototype

Original comment by alex.cre...@gmail.com on 27 Mar 2008 at 8:17

GoogleCodeExporter commented 8 years ago
We have a Rails app that works fine using Prototype 1.6.0.1. When I upgraded to
1.6.0.2 -- thinking, erroneously, that it will result in more stability ;) --
clicking on the calendar did nothing, and the error was output to the Firebug 
console.

The error occurs on Firefox 2 and Firefox 3. In IE 6 and 7, the calendar shows 
up,
but I also receive a similar error, it's just not fatal as in FF (in IE 8, it 
is fatal):

'select(...)' is null or not an object

In FF, disabling Firebug for that page, or disabling the add-on entirely does 
not
help, so I think we can safely assume it is not a Firebug problem.

Original comment by bowma...@gmail.com on 27 Mar 2008 at 12:51

GoogleCodeExporter commented 8 years ago
I am experiencing the same issue with prototype 1.6.0.2, anyone have any ideas?

Original comment by gustint...@yahoo.com on 22 Apr 2008 at 4:09

GoogleCodeExporter commented 8 years ago
I was using Prototype 1.6.0 for the calendar and it worked fine but ever since I
upgraded Prototype to 1.6.0.2 calendar has stopped working. Any idea or work 
around? 

Original comment by shikhamo...@gmail.com on 29 Apr 2008 at 10:04

GoogleCodeExporter commented 8 years ago
It results directly from calendar_date_select.js line 75:
    if (down = this.target_element.down("INPUT")) this.target_element = down;

I tried a few things, poked around a bit, but wasn't able to isolate why. 
(Probably because I don't really know 
what it's supposed to be doing.) However, seems that removing this line makes 
it work with no ill effects, at 
least for my use cases.

Original comment by w...@willglynn.com on 4 May 2008 at 10:24

GoogleCodeExporter commented 8 years ago
I have the same issue.... I tried to remove line 75 as suggested, but it just 
changed
the problem:

too much recursion
[Break on this error] var newElement = Element.build(type, options, style);

Original comment by julien.r...@gmail.com on 16 May 2008 at 9:42

GoogleCodeExporter commented 8 years ago
Thanks everyone for chiming in on the issue.  It seems that prototype 1.6.0.2 
is a problem child or something, I 
haven't had time (made it a priority) to look into the issue myself because I 
still use prototype 1.6.0.1 on all of 
my projects.

If anybody has any clues on this, please share

Original comment by timchar...@gmail.com on 18 May 2008 at 2:58

GoogleCodeExporter commented 8 years ago

Original comment by timchar...@gmail.com on 18 May 2008 at 3:03

GoogleCodeExporter commented 8 years ago
I tried to reproduce this today, and I can't get the same results.  Will 
someone please check out the calendar 
date select demo app?

http://github.com/timcharper/calendar_date_select_demo/tree/master

It comes with prototype 1.6.0.2, and everything is working perfectly.  Not sure 
exactly what the issue is.

Thanks,
Tim

Original comment by timchar...@gmail.com on 22 May 2008 at 5:38

GoogleCodeExporter commented 8 years ago

Original comment by timchar...@gmail.com on 22 May 2008 at 5:39

GoogleCodeExporter commented 8 years ago
my app got a little messy using too many plugins, I think I got fooled by the 
"super
in place controls" that used version 1.10.0 of calendar date select.

I tried to put back prototype 1.6.0.1 to see the calendar working again and had 
the
same bug !

removed everything, re-installed carefully, took the calendar date select from
github, put back protoype 1.6.0.2... and it works now ! that's the problem with 
using
too many javascripts libraries and plugins, and not understand them all....

the calendar is just awsome, so I think the problem occurred between the 
keyboard and
the chair ;) 

cheers

Original comment by julien.r...@gmail.com on 22 May 2008 at 8:11

GoogleCodeExporter commented 8 years ago
Hi Julien,

Thanks for the report :)  Glad to found that you were able to resolve this 
issue.

Best,
Tim

Original comment by timchar...@gmail.com on 22 May 2008 at 4:06

GoogleCodeExporter commented 8 years ago

Original comment by timchar...@gmail.com on 22 May 2008 at 4:06

GoogleCodeExporter commented 8 years ago
For what it's worth, the patch in this rails bug seems to fix the issue:

http://dev.rubyonrails.org/ticket/11102

Original comment by ro...@kyanmedia.com on 26 Jun 2008 at 10:33