Closed Bug 235534 Opened 22 years ago Closed 22 years ago

Browser crashes on Domino Web Access 6.51

Categories

(Core :: XSLT, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: pleugner, Assigned: peterv)

References

()

Details

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040219 Firefox/0.8 When I want to access my mail or calendar on Domino Web Access 6.51 the browser chrashes when it is trying to render the mailbox. Domino Web Access makes heavy use of XML and XSLT to get the data from the Server. An strace showed libtransformiix.so as the last library being loaded, so I assume the problem is in that area. This happens with Firefox 0.8 and Mozilla 1.6. Firebird 0.7 and Mozilla 1.4 worked fine. The URL above can be used to create a Demo Account at Lotus to verify the crash. Reproducible: Always Steps to Reproduce: 1. Open Domino Web Access 2. The Menus get drawn, then the Browser tries to get the XML for the mails 3. Crash Actual Results: All instances of Mozilla or Firefox crash Expected Results: Show my mails
wfm with win2k build 20040224 and the Demo Account. Test URL : http://showcase2.notes.net/mail/mozillaseamonkey.nsf Username: "Mozilla Seamonkey" password "rocks" (active for 7 days)
I don't have any problems with my Moz version (2004012808). No crash, everything seems to work. There is something elso thow... (dunno if this is a reported bug already:) 1) choose in the Webaccessmenu: new->message (maybe you should allow this site to popup) 2) write some text in the edit field for the message contents 3) highlite some written text 4) Click on the text color button result: popup window is moved to the background, and "parent" mozilla window is shown expected: popup window keeps the focus and on top
works now. tested with latest nightlies.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
*** Bug 234501 has been marked as a duplicate of this bug. ***
*** Bug 234619 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.