I upgraded to Firefox 1.5 on Friday night, and DWA no longer works. Mikkel Heisterberg reported the same problem I saw on his blog:
http://blog.lekkim.heisterberg.dk/lekkimworld/2005/12/05/1133786727214.html
Had anyone here loaded a beta of Firefox 1.5? Is it possible that it’s just a setting that needs to be adjusted?
-rich
Subject: DWA Doesn’t Work With Firefox 1.5
Nope – FF 1.5 breaks cross-frame DOM tree calls. See this at Volker’s place:
Subject: RE: DWA Doesn’t Work With Firefox 1.5
Ah… Thanks Stan. I had only caught the fact that Web Admin was broken by Firefox 1.5. And the rest of that thread distracted me, so I didn’t even remember that.
Subject: RE: DWA Doesn’t Work With Firefox 1.5
Yes, the news about Wolfgang Schramm was a bit of a hit. Damned shame. And I hope he recovers completely.
Subject: DWA Doesn’t Work With Firefox 1.5
Hi Richard,Browsing the web over the weekend a blogger mentioned that Lotus is aware of the problem, and their key deveopers are working on it. I don’t recall where I saw that. Somewhat related: I have a few Win2000 machines and Flash no longer works with Firefox 1.5, and of course, many plug-ins no longer work. The best advice for anyone reading this is to skip the 1.5 release for now.
Brian
Subject: RE: DWA Doesn’t Work With Firefox 1.5
Thanks for confirming the Flash issue; I thought I was going insane…
Subject: Mozilla bug reported fixed - for later release?
Followed the Mozilla bug link earlier in this thread, and found it has been logged as “fixed”. I sent an email to the listed owner, to see when it might be in a public release of the product. I saw version numbers that looked like 1.7/1.8 timeframe, but am not sure how they equate with versions of the browser itself.
Anyone have further information?
Subject: RE: Mozilla bug reported fixed - for later release?
The actual fix was catalogued on March 8 in build check-in 1.8.0.2. How that translates to nightlies and releases, I don’t know, but I wouldn’t equate the two numbering schemes (source code and release). The fix will probably be in a 1.5.x update.
Subject: *Fix is released in Firefox 1.5.0.2 (eom)
Subject: Try the Escape key when you get in this state
We’re aware of this problem and we’re working on it. By the way, a simple workaround we have found is to hit the ESCAPE key, when the Edit screen appears to be hung…this seems to get Firefox 1.5 to keep loading the page, and you should be fine.
Starting with Domino 7.0, we employ a much richer “attachments area” which is implemented using XUL. This XUL segment is actually loaded within an IFRAME on the Edit pages. This is the area of the page which seems to be having problems with Firefox 1.5.
We have a couple of standalone files which easily reproduces this issue and we are trying to work with Mozilla folks to figure out details about the apparent regression.
Subject: Still a problem in 7.0.1 but the “Try the Escape key when you get in this state” works
Subject: RE: Try the Escape key when you get in this state
Thanks for the update, Vinod (I hope I have that right – if I have your name reversed, I apologize). Luckily, my own apps are pre-release and look like they can be effectively de-framed, so I don’t have an installed base to worry about, but this was definitely not a bug I needed to see right now. I can’t wait for IE7 to debut…
Subject: Bugzilla pointer to problem
Here’s the bugzilla report outlining the problem causing this issue to DWA edit pages (for Gecko) which employ the XUL attachments area. The 7.0 design has the attachments area initially collapsed which is also contributing to the problem.
Link to Mozilla bug report:
I’m hopeful this will be fixed in Firefox 1.5.0.1
…By the way, bugzilla has a voting mechanism to vote for bugs you really want fixed…I’d urge everyone to vote for this one 