1406986 - Select drop down list in the wrong position with RDM and toolbox docked to side

Status: RESOLVED WORKSFORME

(DevTools :: Responsive Design Mode, defect, P3)

Description

[Rik]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171003144318

Steps to reproduce:

Go on page with a standard select html component. For example here
https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select

- Press ctrl+shif+m (responsive designe mode)
- Press F12 (developer tools)
- Now click the select and the drop down list appears stand alone on the right, out of the html page! :-)



The same thing happen on the contrary.
Get back to Firefox in standard mode (close no responsive design and developer tools).
Open AGAIN (must be reloaded with F5 or with return into the address bar)
https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select

- Press F12 to open the tools
- Press ctrl+shif+m
- Open the select. Now it works despite it is basically the same as before.
- Now press again F12 so that the web developer closes
- Click the select.
Now the select drop down list is again stand alone in the wrong position in the opposite side compared to the previous test.




Expected results:

The select should open with the drop down list just below the button

This happens with Firefox 57.0b6 developer edition. It is OK with Firefox release (v 56.0)
Both 64 bit on Mint 18.

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Can you attach a screenshot / video of the issue?  I have heard of similar issues, but I'd like to be sure I am following your report.

When Responsive Design Mode is open, does the device viewport extend vertically beyond the browser window?  (Or, said another way, does the browser window have a vertical scroll bar?)

Comment 2

[Rik]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> Can you attach a screenshot / video of the issue?  I have heard of similar
> issues, but I'd like to be sure I am following your report.
> 
> When Responsive Design Mode is open, does the device viewport extend
> vertically beyond the browser window?  (Or, said another way, does the
> browser window have a vertical scroll bar?)

It happens regargless of the vertical/horizontal dimension and scroll bar or not.
Screenshot coming soon (I don't see how to attach it here in this reply...)

Comment 3

[Rik]

Attachment: selectprb.png

Comment 4

[Shobhit Chittora]

I can confirm this in my Firefox 56.0 (64-bit). This happens when you click on "Dock to the side of the window" in Dev Tools and then click on switch.

Also I'm looking for good first bugs to contribute to. So if you have anything which you suggest, it'd be much appreciated.

Comment 5

[Rik]

I can also confirm that the problem is not a matter of single or double monitor: I have the same problem both on a computer with single monitor that on double monitor.

FF 56 is fine for me, only v 57 has the problem

I notice that the dropdown look of the "select" in FF 57 has a new more modern look than FF 56. Maybe the problem is just something in the select component.

Comment 6

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Thanks for the screenshot, I can reproduce now!

It's specific to using DevTools in dock to side mode only, it seems.  (I usually use dock to bottom, so that's what I was missing!)

Comment 7

[Rik]

Ah OK, I didn't even remember that the default is the tools on the bottom. :-)

Comment 9

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals

Comment 10

[Rik]

I can confirm the bug is still there on the vers. 61.0b9 (64-bit).

Comment 11

[Rik]

In version 67.0b5 (64-bit)
it's even worse because no matter the order of F12 and ctrl+shif+m, it's always not working properly in both cases.

In the age of "mobile first", the tools windows better fit on the side than on the bottom of the screen (unless you have a vertical monitor).

Comment 12

[Rik]

V. 82: I've tested this morning and the problem seems to be fixed

Comment 13

[Rik]

[Tracking Requested - why for this release]: