654520 - scrollintoview() not used correctly if object is hidden under status bar or horizontal scroll bar

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Geran Smith]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest-3.6/win32/en-US/Firefox%20Setup%203.6.17.exe

I am using Rational Functional Tester (an automated testing tool) which calls the scrollintoview() method in Firefox if an object is not in the current view panel. If the object which needs to be scrolled in to view is hidden under the status bar or the horizontal scroll bar, then the object is not "in view" as RFT is unable to click on the object.

Reproducible: Always

Steps to Reproduce:
1. Enable the Status Bar if disabled
2. Place "buttonTest.html" in the root of your C:\ drive or modify the code in the file to launch buttonTest2.html
3. Open buttonTest.html
4. Click "RFT Cannot Click OK(190)!"
5. In the new window that appears, observe that the OK button is obscured by the status bar and the horizontal scroll bar
6. In this case, when RFT calls the scrollintoview() method in Firefox, Firefox does not scroll the button to a place where it can be interacted with

Actual Results:  
RFT is unable to click on the OK button because the status bar or the horizontal scroll bar is blocking the button from view

Expected Results:  
Firefox should scroll the button either above or below the status bar and the horizontal scroll bar. This will allow RFT to find the object.

I did create a workaround that works for now. The tester needs to disable the status bar and use the addon "Stylish" to remove the horizontal scroll bars.

Comment 1

[Geran Smith]

Attachment: Contains buttonTest.html and buttonTest2.html

Comment 2

[Maurya Talisetti]

Using: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110512 Firefox/6.0a1

There's no status bar from Firefox 4 onwards. So, is this bug still relevant?

Btw, I had trouble opening the attachment. I displays strange characters.

Comment 3

[Geran Smith]

Attachment: Updated buttonTest.html and buttonTest2.html

The content type for the original file was incorrect. Uploading it again to see if it works now.

Comment 4

[Geran Smith]

(In reply to comment #2)
> Using: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110512 Firefox/6.0a1
> 
> There's no status bar from Firefox 4 onwards. So, is this bug still relevant?
> 
> Btw, I had trouble opening the attachment. I displays strange characters.

In Firefox 4 we now have the addon bar on the bottom, so that will 'replace' the status bar from Firefox 3.6 for this bug. Either way, the bug is still relevant, as the horizontal scroll bar will block buttons still.

Also, I uploaded a new version of the zip, I confirmed it works.

Comment 5

[abacon]

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0a2) Gecko/20110513 Firefox/5.0a2
Win7 64bit.

Tried the test case and it works fine. However, if you attempt to use the horizontal scrollbar after the modal dialog pops up, the view is returned to the top of the page. Because there's no vertical scrollbar, you can't scroll back down to where the OK button is in order to dismiss it. This occurs for all of the tests in the attached zip.

Comment 6

[Geran Smith]

(In reply to comment #5)
> Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0a2)
> Gecko/20110513 Firefox/5.0a2
> Win7 64bit.
> 
> Tried the test case and it works fine. However, if you attempt to use the
> horizontal scrollbar after the modal dialog pops up, the view is returned to
> the top of the page. Because there's no vertical scrollbar, you can't scroll
> back down to where the OK button is in order to dismiss it. This occurs for
> all of the tests in the attached zip.

What automation tool were you using when you tested this?

Comment 7

[u279076]

I believe this was manually tested using the information and testcases you provided.

Comment 8

[Geran Smith]

(In reply to comment #7)
> I believe this was manually tested using the information and testcases you
> provided.

I first ran into this issue when using Rational Functional Tester with Firefox. Unless you are manually calling the scrollintoview() for Firefox, I don't think that the reproduction failure will count. Here is a set of reproduction steps that makes it a little more clear:

Steps to Reproduce:
1. Enable the Status Bar if disabled
2. Place "buttonTest.html" in the root of your C:\ drive or modify the code in the file to launch buttonTest2.html
3. Open buttonTest.html
4. Click "RFT Cannot Click OK(190)!"
5. In the new window that appears, observe that the OK button is obscured by the status bar and the horizontal scroll bar
6. Using Rational Functional Tester, record a click on the OK button
7. To reproduce the failure in playback, click the "RFT Cannot Click OK (190)!" button in buttonTest.html then try to playback the script in RFT
8. In this case, when RFT calls the scrollintoview() method in Firefox, Firefox does not scroll the button to a place where it can be interacted with

Comment 9

[Geran Smith]

(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #7)
> I believe this was manually tested using the information and testcases you
> provided.

Anthony, if you need me to show this to you via a remote session, I would be willing to do so.

Comment 10

[u279076]

@Geran, are you able to reproduce this manually, or is it only from within Rationale?

Comment 11

[Geran Smith]

@Anthony I don't know how I would reproduce this manually, it is related purely to how Firefox is reporting to Rational Functional Tester that an object is on screen or not.

Comment 12

[u279076]

Okay, so this is not a user-facing bug. That's all I was trying to figure out. I personally do not have a lot of time to debug bugs which does not affect the average end-user.

Geran, if you are willing to help debug this on your end, it would be appreciated.

Sorry I can't be of more help.

Comment 13

[Geran Smith]

Anthony, what do you need me to do to debug this? I am not a developer, so I don't have the expertise to dive into the code to look for a specific place in Firefox where this happens.

Comment 14

[u279076]

(In reply to Geran Smith from comment #13)
> Anthony, what do you need me to do to debug this? I am not a developer, so I
> don't have the expertise to dive into the code to look for a specific place
> in Firefox where this happens.

I don't know the code well enough either. It will need to wait until a Firefox developer has had a chance to look at this bug.