User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199pre) Gecko/20070604 Firefox/188.8.131.52 Navigator/9.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206pre) Gecko/20070604 Firefox/220.127.116.11 Navigator/9.0b1 www.blackboard.com and more specifically ccc.blackboard.com does not allow firefox to be used for posting in the forum area. This is an online classroom used by increasing numbers of schools with the numbers of students easily within tens of thousands. When the specific threads are accessed perhaps only for new ones created the title bar within the body of the page displays but does not respond. All of firefox becomes frozen on that view despite the unapparent control over which tabs are displayed. When Firefox is closed the process remains running and disallows new browsers to be opened until it is closed through non graphical OS interface means. Reproducible: Always Steps to Reproduce: 1. go to existing topic 2. add new thread 3. attempt to title it Actual Results: frozen firefox Expected Results: a new thread within the topic This also happened with Netscape 9 beta (running on Firefox 2 engine)
is there a java applet on that site? Why are you pointing to a Java related incompatibility? Could you post your version of FLASH plugin and JAVA plugin (you can read versione number from address about:plugins)
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.