-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
In some cases bootstrap-modal does not work #240
Comments
Hm... that's pretty vague. Can you give more information? I haven't run into any issues with it. How are you using? Could you provide a code example? maybe a jsfiddle? |
in this place:http://twitter.github.com/bootstrap/javascript.html. The problem does exist, my English is not good, not well described |
Yep i see. Thanks, taking a look now |
Works now - thanks for reporting! |
In this place:http://twitter.github.com/bootstrap/javascript.html, the problem does exist. You can reproduce this problem: |
hard refresh firefox -- it works for me now |
hard refresh, reload, clean cache, I have done. No, there are still problems Re-tried many times. you can try:Non-stop hits and non-stop press escape key. |
can you check something for me. if you go to this page: http://twitter.github.com/bootstrap/1.3.0/bootstrap-modal.js can you search for |
oh wait -- do you mean, click the button 1million times really fast? |
I can see 'force reflow'. click button and press esc key, qucikly, non-stop |
yeah i see what you mean... looking into that |
I'm having this issue as well. I can provide additional information as necessary, just ping me. |
just a heads up, if you don't use animation this bug isn't present. It only occurs in firefox because they are dropping css animations as an optimization when you trigger many really fast. |
@fat Do we close this or wait to fix it in dev or 2.0-wip? |
It's still a problem. I haven't figured out a way to fix it in firefox. :( |
i was able to get the same problem on chrome too, but much less frequently. I'm working around the problem by disabling animation on modal. |
Fixed in dev - this will be released with 1.4 |
Thanks fat! |
no problem :) |
I am using 1.4 and the modal usually fails on Firefox and IE. I removed the fade class for the time being, but it doesn't look nearly as good... |
@tmcallister are you using these steps to reproduce: #240 (comment) ? I ask because i definitely saw this issue happening frequently in Firefox 8.0.1 (mac) but after @fat 's close on the 31st i've not seen it again. |
@tmcallister can you confirm you're using the lastest code from master? I don't see how it could be possible with the current implementation |
@mariozig it usually fails on first attempt. Same behavior, it just doesn't display. @fat I have just tried both live linking to 1.4.0 and also pulled down latest code. Same behavior with either. More info: I develop on a Mac
I test windows browsers in a Fusion VM using Windows XP.
I have field reports from alpha users (using WIndows browsers) that the modal usually does not work in newest versions of FF and IE9. Field reports it works in Chrome. |
Not sure what you code looks like but I was having the same problem in FF, when I would click on the link it would not work the first time but the second click it would work. Anyhow I update my call to include "show" and it works on the first click now. $("#dialog").modal({show:true, backdrop:true}) Not sure if it will help but it fixed it for me. |
Heres the generated code. Please excuse some of the goofy names, its test data. As discussed in this thread, removing the fade class totally eliminates the problem. Maybe there is something wrong in the code :-/
|
I can properly view the demo page modal using the various browsers I reported on above. Thats pretty clear evidence the problem is on my side. I'll try and troubleshoot. Thanks for responding so quickly. |
I'm not sure why this is, but the problem does exist.
If I do not set ‘keyboard’ option, it can be normal.
The text was updated successfully, but these errors were encountered: