Skip to content

Fix problems with content async ajax request #1272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

lotjuh
Copy link

@lotjuh lotjuh commented Jun 16, 2014

There were 2 problems, first af all, the check for "ui-tooltip-open" was done -before- the _delay call. This means that when the _open function was actually called, the user could have already moved his mouse out.
I've moved the check to the start of the _open function because I believe that's where it should actually always be checked.
Second, the mouseout events were only set in the _open function. This way, with the async ajax request, the mouseout events were never called when the tooltip wasn't actually opened (the user moved the mouse away before the content was able to update). I've set the events in the open function now as well.

Should fix #8740

There were 2 problems, first af all, the check for "ui-tooltip-open" was done -before- the _delay call. This means that when the _open function was actually called, the user could have already moved his mouse out.
I've moved the check to the start of the _open function because I believe that's where it should actually always be checked.
Second, the mouseout events were only set in the _open function. This way, with the async ajax request, the mouseout events were never called when the tooltip wasn't actually opened (the user moved the mouse away before the content was able to update). I've set the events in the open function now as well.
@tjvantoll
Copy link
Member

Hi @lotjuh,

Thanks for taking the time to contribute to jQuery UI. We have the following requirements of pull requests before we can review them.

  • Sign our CLA.
  • Include a unit test to ensure the fix works and prevent against regressions.
  • Ensure commit messages adhere to our commit message style guide.

I'm going to close this for now, but feel free to send another PR after addressing these points. You might also want to check out #1053, which is another pending PR that addresses this issue.

Thanks.

@tjvantoll tjvantoll closed this Jun 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants