Note: bugzilla.mozilla.org in its new environment and things are being tested right now. Exercise caution until further notice.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:22.214.171.124) Gecko/20101203 Firefox/3.6.13 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:126.96.36.199) Gecko/20101203 Firefox/3.6.13 http://stackoverflow.com/questions/4225668/jquery-modal-popup-firefox-flicker/4272833#4272833 The above link gives more information as to the issue I am experiencing. Basically, when you are viewing an ajax enabled site and there is a drop down list on the page the page will flicker on an async postback if the listbox; one, has more than 20 items, and two, any item past the 20th item is selected. The 20 items might not be arbitrary. The default number of viewable items in a drop down list on FF is 20. There is something happening when the control is rendered back on the page after the async postback. In my example I was using MS Ajax but in another person's example he was using JQuery. I hope this is useful. Reproducible: Always Steps to Reproduce: 1.Create ajax enable page with drop down list containing more than 20 items 2. selected the 21 items and fire an async postback 3. page will flicker white Actual Results: Page flickered white Expected Results: Page should not flicker
Here is another forum link where I posted the issue. http://forums.asp.net/p/1626835/4190536.aspx#4190536
Please post a html testcase using the "add an attachment" link above or provide a public url
I have posted a url with a few samples. Thanks!
It would be still great to have a minimal testcase attached to this bug.
And so far I haven't managed to reproduce the problem on trunk/linux when testing http://www.mjharris.com/debug/. Though, I'm not sure I didn't test it right. How should I select something in the <select>? Using mouse? keyboard? mouse+keyboard?
I can't see flickering with Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101212 Firefox/4.0b8pre SeaMonkey/2.1b2pre
Okay I promise I am not going crazy! I did not upload a test case project but you can download it from the url provided. There is a link at the bottom of the page. I thought I had posted enough information on how to reproduce, but maybe not. User must fire an async postback. That is the purpose of the two buttons (link button 1 and link button 2) Each button is inside its on update panel. I have selected values in both the listbox and drop down box that are beyond the default viewable area of the control. Thus if the first item were selected, then you would have to scroll to get to that item. I am running Windows 7 on a Pent. 4 with 3GB of ram. I just tested the page on my Macbook Pro and it did not flicker using Firefox. Not sure if that means anything accept that my computer at the office is slow. It could be a speed issue, but that doesn't make sense since I have every browser installed and FF is the only one that flickers. Hope this helps!
There is no flickering with Seamonkey trunk (Gecko2.0pre) but I can see it in Gecko1.9.2. Can you please retest with Firefox4.0beta7 or later builds ?
Matthias, I will test the beta when I get back from my meeting tonight. I am assuming that I can download that from the FF site. Also, I have made a video which I uploaded to the site. Link is at the top of the test site if you want to see the flicker on my desktop. Quality is not the best but it should work.
Mozilla/5.0 (Windows NT 6.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 I have just installed 4.0b7 and am happy to report that the flickering has gone away. So I am not sure if you all want to try and fix this for the current version. Not sure when ver 4 is schedule to be released.
FF3.6.x is in the maintenance mode, it gets security fixes only. Minor bugs like this one aren't fixed on this branch anymore. I will go ahead and mark this worksforme because it's already fixed. Thanks for this bug report and your work with creating a testcase !
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.