revlets and ajax

Bringing the internet highway into your project? Building FTP, HTTP, email, chat or other client solutions?

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
sturgis
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 1685
Joined: Sat Feb 28, 2009 11:49 pm

revlets and ajax

Post by sturgis » Sat Jan 02, 2010 8:15 am

i have a quick question regarding revlets. I have a site at http://runthenumbersnow.com/ that i'm experimenting with. In the page I have 2 revlets, one for the header and clock across the top, and one where I was trying some things with ajax. In safari, the google search revlet works fine, no hitches other than the fact I havn't set the revlet up yet to handle more than one search term (be aware of that if you test)

With firefox on the other hand, the first time I do a google search, both revlets reset, and reload. Subsequent searches don't cause this behavior, a page reload is required to make it occur again.

Anyone have a clue how to fix this?

I haven't tried it in IE either, so don't know if it works there.

sturgis
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 1685
Joined: Sat Feb 28, 2009 11:49 pm

Re: revlets and ajax

Post by sturgis » Sat Jan 02, 2010 8:03 pm

Just noticed another part of the behavior, if I do search for more than 1 term using the google search revlet this makes all revlets on the page reload also, so I think I have an idea of where to look. Will update if I solve it.

sturgis
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 1685
Joined: Sat Feb 28, 2009 11:49 pm

Re: revlets and ajax

Post by sturgis » Sat Jan 02, 2010 8:10 pm

nope, but now multiple search terms work fine. Still no idea why the first search causes a firefox page reload and not safari. I also noticed, safari shows the search box at the bottom of the page from the google site, firefox doesn't so i'm guessing it has something to do with the page structure itself. If I had hair i'd pull it out!

edit: Changed to an iframe instead, problem solved. Apparently something I was doing to the page structure the old way was making things choke, hence the initial reload problems. Go figure.

Post Reply