Update:
It doesn't seem to have anything to do with single quotes or commas,
for that matter, inside the JSON data.
Now HERE'S something to make you scratch your head:
I have now put the complete data file back up in the external file
('CANADA_3.js') and I have ALSO put the EXACT same data file into the
static var included inline in the HTML page ('list3').
This is the best demonstration of the problem: The external file and
the static var both load fine if using Firefox. Only the static var
works for IE.
Live page (will not change until further response):
http://jamestilberg.com/jquery/
James
?????
On Feb 1, 11:22 am, James <james.tilb...@gmail.com> wrote:
> @Mike
> Thanks. But it should have been working with the default code since
> dropdown 2 was working - dropdown 3 used the exact same principle.
> There is definitely something going on different between FF and IE.
>
> Question - Could the existence of single quotes within the JSON data
> throw off JQuery? example: If one of the cities is "O'Brien"....
>
> I ask because I have now put up a refined page with the two methods
> and I have used a smaller version of the data file and guess what? It
> now works. So this leads me to believe the JSON data itself may have
> been causing a problem with IE only (Firefox always worked).
>
> http://jamestilberg.com/jquery/
>
> The thing is, I had already validated the JSON data with several
> different online JSON validators....
>
> I guess I need to build the JSON file back up and see if something
> specific stumps JQuery...
>
> On Feb 1, 2:01 am, Mike Nichols <nichols.mik...@gmail.com> wrote:
>
> > @James
> > Thinking about what you are doing here with the third dropdown...By
> > attaching that dropdown to the second you are telling it to be
> > filtered by the second dropdown's selected value...which is not
> > selected yet since it just loaded so I would presume you shouldn't
> > have any data in the third drop down.
> > To support this behavior in the past I used the 'event' property of
> > the options to define which event actually fires a cascade ( the
> > defalt is 'changed'). Then I manually fire cascade within the parent
> > element's change handler. :
> > //when 'make' is selected...
> > $(".seconddropdown")
> > .cascade(".firstdropdown",{
> > ajax: 'firsturl.js'
> > })
> > .bind("change",function() {
> > $(this).trigger("custom.changed");//manually call cascade
> > });
>
> > $(".thirddropdown")
> > .cascade(".secondbehavior",{
> > event : "custom.changed",//bind to custom event to prevent
> > loading
> > from cascade
> > ajax: 'secondurl.js',
> > });
>
> > On Jan 31, 4:39 pm, James <james.tilb...@gmail.com> wrote:
>
> > > I am new to JQuery and your cascading dropdown was exactly what I was
> > > looking for. After formatting my data in JSON I have tested out the
> > > Chained example (http://dev.chayachronicles.com/jquery/cascade/
> > > index.html) and it ONLY WORKS in Firefox and NOT IE.
>
> > > I am attempting to load the data from two external files, while your
> > > example loads the second data set from a static var.
>
> > > Is there a further step necessary to get this to work in IE?
>
> > > I have my working example at:http://jamestilberg.com/jquery/
>
> > > Any help would be appreciated! :)
