Link to home
Start Free TrialLog in
Avatar of Larry Vollmer
Larry Vollmer

asked on

Problem with form

I have this page:
http://tinyurl.com/8bo5a3c

There is a widget that lets a user enter their email address. When you hit submit, a shadow highlights the input box for a second. I want to remove this feature, but I have no idea where it is coming from. I could use a second set of eyes.
Screen-shot-2012-08-28-at-9.43.4.png
Avatar of dimmergeek
dimmergeek
Flag of United States of America image

Do you have code we can look at?
Specifically the 'On Submit' event...
Avatar of Larry Vollmer
Larry Vollmer

ASKER

Sure, here is the code from the page in question.
code.txt
ASKER CERTIFIED SOLUTION
Avatar of Julian Hansen
Julian Hansen
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The color appears to be #49413C and it looks like this might be baked into Gigya's jQuery code.  It's not uncommon for something like this to be present as a visual cue to the client that the AJAX request is processing.  You could try tinkering with the code, but I would be inclined to go directly to Gigya support and ask them about the behavior.  They may have an easy way to make it transparent or change the color scheme to something you like better.
Julian - when I remove that block of code, the form does not submit .

Ray - you may be right . I will look into this.
Did you remove the entire BeforeSend bit?

Can you post the resulting function you were left with after you removed that code - should not have stopped you submitting.
Julian - I investigated some more and i think the problem was that I also needed to remove the unblock line.

When I remove both of those, it works as intended.
Interesting - I wonder why the unblock statement would stop the form from being submitted when it is in the complete function?

As I understood it the .block in the beforeSend was there to ensure the form was not submitted again by "covering" the submit and that the .unblock in the complete function removes the "cover".

I assumed calling unblock would have no effect if it was not already blocked (like calling show on a visible element).

Anyway live and learn - thanks for the points
Thanks for the help. I don't think it was stopping the form from submitting. I incorrectly assumed that because my local was taking so long to respond. After ten seconds or so, it actually did submit.
Oh ok - that makes sense.