888914 - Bottom of page hidden with Dev Tools open

Status: RESOLVED WONTFIX

(DevTools :: General, defect)

Description

[Evan]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130625125232

Steps to reproduce:

1. Go to a short website, i.e. something that doesn't require scrolling.
2. Open developer tools.


Actual results:

The bottom of the page is hidden by developer tools. You cannot scroll to see it. The only workaround is to close and re-open the developer tools.


Expected results:

The page should become scrollable, so I can always see the bottom of the website with the dev tools open.

Comment 1

[Panos Astithas (he/him) [:past] (please ni?)]

Need specific steps to reproduce the problem. Which website? Which tool? It doesn't happen on this website for example: http://htmlpad.org/debugger/

Comment 2

[Tiziana Sellitto [:tiziana]]

(In reply to Panos Astithas [:past] from comment #1)
> Need specific steps to reproduce the problem. Which website? Which tool? It
> doesn't happen on this website for example: http://htmlpad.org/debugger/

I've tested it on your link and others for example (https://bugzilla.mozilla.org/), if I resize the windows the scroll-bar appears even if at first it wasn't present but it didn't cover text only the background color.
I didn't notice before, sorry!

egtann can you provide an url where the scrollbar doesn't appear?

Comment 3

[Evan]

Try this: https://squirr3l.herokuapp.com/

Hit 'Get Started' then open the dev tools. It's undoubtedly due to some odd CSS, but it still seems to be an unexpected behavior.

Comment 4

[Tiziana Sellitto [:tiziana]]

I cannot see the scrollbar even without hit "Get Started" and opening the dev tools if I resize the window.
The same behavior happens in Chrome and Safari.

Comment 5

[Paul Silaghi, QA [:pauly]]

(In reply to Tiziana Sellitto [:tiziana] from comment #4)
> I cannot see the scrollbar even without hit "Get Started" and opening the
> dev tools if I resize the window.
> The same behavior happens in Chrome and Safari.
Agreed. This is a site issue and not a Firefox one.

Comment 6

[Evan]

(In reply to Paul Silaghi [QA] from comment #5)
> Agreed. This is a site issue and not a Firefox one.

Paul, if Firefox's developer tools respond in an unexpected way on (any) site, it's a Firefox problem. If other browsers experience the same behavior, that doesn't mean it isn't a bug within Firefox—but rather a bug in all of the browsers.

The expected behavior is to enable scrolling when the browser window becomes smaller upon opening dev tools. That doesn't happen, and that's a Firefox issue. It just so happens that it's also a Chrome and Safari issue, but it's an unexpected behavior (in all cases) that deserves to be solved regardless.

Comment 7

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

(In reply to Evan from comment #6)
> (In reply to Paul Silaghi [QA] from comment #5)
> > Agreed. This is a site issue and not a Firefox one.
> 
> Paul, if Firefox's developer tools respond in an unexpected way on (any)
> site, it's a Firefox problem. If other browsers experience the same
> behavior, that doesn't mean it isn't a bug within Firefox—but rather a bug
> in all of the browsers.
> 
> The expected behavior is to enable scrolling when the browser window becomes
> smaller upon opening dev tools. That doesn't happen, and that's a Firefox
> issue. It just so happens that it's also a Chrome and Safari issue, but it's
> an unexpected behavior (in all cases) that deserves to be solved regardless.

It is not unexpected, the browsers are simply obeying the sites CSS rules that specify that there should be no scrollbars.

The following 2 rules cause the issue:
html {
  overflow: hidden;
}

desktop {
  ...
  overflow: hidden;
  ...
}

Comment 8

[Paul Rouget [:paul]]

We thought before about covering the content instead of resizing it. But we think it's way too confusing (window size not changing from the page point of view, but resizing from the user point of view).

Comment 9

[Evan]

You're right; that's still confusing.

Instead, what if it showed a notice in the dev tools or highlighted CSS in the Inspector that could be problematic—just as you did above, Mike. I could have figured the rest out.

But here, it wasn't behaving how I expected it to—and it shouldn't, you're right—but it should tell me why.