419533 - Lotus Domino Web Access on Trunk, no scroll bar

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Morris-moz]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b4pre) Gecko/2008022504 Minefield/3.0b4pre
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b4pre) Gecko/2008022504 Minefield/3.0b4pre

I run into it using Firefox 3b3/Trunk and Lotus Domino 7.0.2 on OS X whereas Firefox 2.0.0.12 works just fine. It makes Lotus Notes / Domino barely usable in Firefox 3. You can only see the most recent mails for instance since there is no way to scroll down.

It could be related to #306609 and regressed on Trunk compared to Firefox 2.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Morris-moz]

Attachment: Screenshot showing the different scrollbars

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Is there a public instance we can use to see what's causing it, or any way you can provide a reduced testcase?

Comment 3

[Mike Beltzner [:beltzner, not reading bugmail]]

Not blocking until we can confirm - if there's a place where we can look into this, or a reduced testcase (a HTML snippet that shows the problem) please renominate.

Comment 4

[Morris-moz]

The reason I asked for blocking is to get it on the radar and hopefully someone with access to a Lotus 7 installation would see it as well. I appreciate it can't really block FF3 without any verification or possible leads to the cause. I'm sure you understand I cannot give out my user name and password for a Lotus network that has over 100K users and spans offices in 48 countries. I'd not only get fired, I would most likely be sued as well.

I am trying to find the complete source of the page, so far I only seem to get some sort of frame page source, not the actual code that is the culprit. If anybody has tips to get to see more source code from complicated pages like this I would be happy to give it a try and post the result here.

It is most likely an issue with Lotus Domino Web Access 7 and not Firefox' fault. The page does not only render in quirks mode, it causes a number of scripting errors as well. Instead of IBM using standard scroll bars they've decided to built their own, which is likely the cause of this problem. However, Firefox 2 was able to handle it so maybe it is an issue that surfaced after the switch to Cairo.

As for the urgency, although it is technically a regression (it works in Firefox 2), it might not be worth blocking Firefox 3. It will probably start to cause bigger issues when the automatic major update is pushed and the masses automatically update from Firefox 2 to Firefox 3. Sadly even Safari can't handle this so OS X users have to rely on Firefox 2 for now. I believe somewhere just after the release of FF3 final would be an acceptable timeframe to look into this, and likely with a lot more eyeballs as well...

Comment 5

[Morris-moz]

Attachment: The source of the page.

Some parts of the source are missing because some elements are loaded from other pages but the general lay out seems to be there.

Comment 6

[Morris-moz]

Attachment: A screenshot of the page, to help understand the source.

Comment 7

[Morris-moz]

Attachment: A screenshot to show how the scroll bar looks in Firefox 2.0.0.12

Comment 8

[mws]

I have this same problem with Lotus Domino Web Access.  Unfortunately the installation for my workplace is not public.  My workplace is using version 6.5.6 but the scrollbar looks exactly the same as the screenshots in the attachments.

This problem is on OS X but not Windows.  It is still a problem in 3.5 and trunk.

The code is too difficult for me to create a test case.  Firebug was a big help but I'm having real trouble even getting a working test to start reducing.  Hopefully someone more experienced than me could look at this.

Anyway the clue I can give is that Firebug shows that its a XUL <scrollbar>?
The scrollbar code is:

<div style="overflow: hidden; width: 15px; height: 100%;"><scrollbar orient="vertical" style="height: 100%;" curpos="0" nId="0" maxpos="41802.82608695652" increment="17.217391304347824" pageincrement="379.7826086956522"/></div>

<scrollbar> is styled by chrome://global/skin/scrollbars.css and chrome://global/content/xul.css

Comment 9

[mws]

This is a duplicate of bug 306609.  However, reading the bugs it is duped and related to claim to have fixed the problem since Firefox 3 but I had this problem with Firefox 3.5 with Louts Domino 6.5.6 and there is a comment in bug 306609 that it was a problem with Firefox 3b3 in Lotus Domino 7.

Possibly the several levels of duplicates may have failed to catch this case?  Bug 306609 may need to be reopened to give this problem some visibility.

My workplace recently upgraded to Lotus Domino 8.0.2 which does not exhibit this problem.

Comment 10

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You may also wish to try with the latest Firefox 4 beta, http://www.mozilla.com/en-US/firefox/all-beta.html.

Comment 11

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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.