1288409 - The top part of the RDM modal is unreachable if the Firefox window is resized

Status: RESOLVED DUPLICATE of bug 1498492

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

Description

[Mihai Boldan, QA [:mboldan]]

[Affected versions]:
- Firefox 50.0a1 (2016-07-21)

[Affected platforms]:
- Windows 10 x64, Mac OS X 10.9.5, Ubuntu 16.04 x64

[Steps to reproduce]:
1. Launch Firefox.
2. From about:config, enable the devtools.responsive.html.enabled pref.
3. Enable RDM.
4. Click on the "Edit list..." button from the devices list in order to open the modal.
5. Resize the window.

[Expected result]:
- The modal can be entirely if the page is scrolled.

[Actual result]:
- The top part of the modal is unreachable. See http://imgur.com/a/6nH7t .

[Regression range]:
Last good revision: 9ce31e9f90cb0e534611b0f617c5bbc232ffe748
First bad revision: 6a441b2b2997cdbd47b5d80283f6f60d5a9e7489
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=9ce31e9f90cb0e534611b0f617c5bbc232ffe748&tochange=6a441b2b2997cdbd47b5d80283f6f60d5a9e7489
I think that Bug 1262839 caused this issue.

Comment 1

[Andrew Overholt [:overholt]]

Marco, does P3 mean this regression will be fixed in 50?

Comment 2

[Marco Mucci [:MarcoM]]

(In reply to Andrew Overholt [:overholt] from comment #1)
> Marco, does P3 mean this regression will be fixed in 50?

Hi Andrew, this bug is on our low-priority reserve list as the team is still working on the MVP project bugs.  I can't say when they would be able to address it.

Comment 3

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

(In reply to Andrew Overholt [:overholt] from comment #1)
> Marco, does P3 mean this regression will be fixed in 50?

This is a bug in a feature that is disabled by default, for additional context.

Comment 4

[Andrew Overholt [:overholt]]

(In reply to Marco Mucci [:MarcoM] from comment #2)
> (In reply to Andrew Overholt [:overholt] from comment #1)
> > Marco, does P3 mean this regression will be fixed in 50?
> 
> Hi Andrew, this bug is on our low-priority reserve list as the team is still
> working on the MVP project bugs.  I can't say when they would be able to
> address it.

OK. We have a relatively recently-adopted "no regressions" policy so normally I would push back here, but jryans clarifies below so I think we're good. Thank you.

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #3)
> (In reply to Andrew Overholt [:overholt] from comment #1)
> > Marco, does P3 mean this regression will be fixed in 50?
> 
> This is a bug in a feature that is disabled by default, for additional
> context.

I think we should mark this as won't fix for 50, then, if that's ok with you. Thanks.

Comment 5

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

(In reply to Andrew Overholt [:overholt] from comment #4)
> I think we should mark this as won't fix for 50, then, if that's ok with
> you. Thanks.

Sure, seems logical.

Comment 6

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

Bug in disabled feature under development, removing regression keyword.

Comment 8

[Martin Balfanz [:mbalfanz]]

This issue has been filed a couple of times. I will mark it as duplicate of bug 1498492, mainly because this one is already assigned.