Open Bug 1284245 Opened 5 years ago Updated 2 years ago

Iframes list is overlapping the Toolbox buttons

Categories

(DevTools :: Framework, defect, P3)

defect

Tracking

(firefox47 unaffected, firefox48 unaffected, firefox49 wontfix, firefox50 wontfix, firefox51 wontfix, firefox52 fix-optional, firefox53 fix-optional)

Tracking Status
firefox47 --- unaffected
firefox48 --- unaffected
firefox49 --- wontfix
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 --- fix-optional
firefox53 --- fix-optional

People

(Reporter: JuliaC, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [reserve-html])

Attachments

(3 files)

[Affected versions]:
- latest Nightly 50.0a1 (2016-07-03)
- latest Aurora 49.0a2 (2016-07-03)

[Affected platforms]:
- Windows 10 x64
- Ubuntu 14.04 x86
- Mac OS x 10.11

[Steps to reproduce]:
1. Launch Firefox with a new profile
2. Hit Ctrl+Shift+I (or Cmd+Opt+I) in order to open the Toolbox
3. Click the frame selection command button ("Select an iframe as the currently targeted document")
- inspect the iframes list

[Expected result]:
- The iframes list is displayed properly and all the Toolbox elements are visible

[Actual result]:
- The iframes list is overlapping the Toolbox buttons (see attached screencast)

[Regression range]:
- Last good revision: 3435dd7ad71fe9003bdeee18fd38d815e033beef
- First bad revision: dc4d7f68030e9edd22ad0bb0bd2244d047dd767d
- Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3435dd7ad71fe9003bdeee18fd38d815e033beef&tochange=dc4d7f68030e9edd22ad0bb0bd2244d047dd767d

Triggered by Bug 1266419 

[Additional notes]:
- Beta and RC builds are not affected
Depends on a solution from Bug 1274551.  The frames list is being opened at a hardcoded x/y position and when the menu shows up on top it covers up the toolbox.

Does this happen on any page with frames (even if it just has 1) or only if it has a lot of frames as in the screencast?
Blocks: 1266419
Depends on: 1274551
Flags: needinfo?(iulia.cristescu)
Whiteboard: [devtools-html] [triage]
Component: Developer Tools → Developer Tools: Framework
Priority: -- → P1
I think it's too early to prioritize this since it's awaiting triage
Priority: P1 → --
Severity: normal → enhancement
(In reply to Brian Grinstead [:bgrins] from comment #1)

> Does this happen on any page with frames (even if it just has 1) or only if
> it has a lot of frames as in the screencast?

Hello! Yes, indeed, this issue affects only the pages with lots of frames.
Flags: needinfo?(iulia.cristescu)
Flags: qe-verify+
Priority: -- → P3
Whiteboard: [devtools-html] [triage] → [reserve-html]
QA Whiteboard: [qe-dthtml]
Priority: P3 → P2
Assignee: nobody → rchien
Status: NEW → ASSIGNED
Attached image nightly build 1.png
arni2033, do you still see that issue happened in latest nightly? I didn't saw any overlapping on my local nightly build (see my attachment)
Attachment #8775039 - Flags: feedback?(arni2033)
Comment on attachment 8775039 [details]
nightly build 1.png

>>>   My Info:   Win7_64, Nightly 50, 32bit, ID 20160726080520 (2016-07-26)
On my Windows 7 I see exactly the same (see attachment 8771600 [details]). Url for testing:

data:text/html,<script>S="<iframe></iframe>";for(i=0;i++<7;)S+=S;location="data:text/html,"+S</script>
Attachment #8775039 - Flags: feedback?(arni2033)
Yeah! I reproduced it on Mac by shrinking firefox window to fit half of my laptop screen and moving firefox to the left of my screen too. Iframes list will overlap on toolbox buttons once clicking button.

I suspected that root cause is around in toolbox.js at [1] which calculates menu X, Y position.


[1] https://dxr.mozilla.org/mozilla-central/source/devtools/client/framework/toolbox.js#1653-1656
I suspect that affected commit is https://hg.mozilla.org/mozilla-central/rev/62ce2708b5be.

It updated menu APIs part so would be the most suspicious one to cause this regression.

However, it is unable to be verified by reverting this patch since it caused other conflict. I'll look at this patch and see what we can do.
Oh, I should be aware of comment 1 mentioned and it told this solution will depend on bug 1274551.

I think we should wait for bug 1274551 and hear the feedback for Honza since he probably have a better idea for how to deal with it. Unassigned myself from now.
Status: ASSIGNED → NEW
Assignee: rchien → nobody
Joe, please help triage this for 49.
Flags: needinfo?(jwalker)
I think this is fix-optional.  We could uplift if Bug 1274551 is fixed in time, but it's only triggering in pages with a lot of iframes
Priority: P2 → P3
No work on this since this was last triaged. Let's update the release tracking flags.
Seems highly unlikely that bug 1274551 will get fixed in time to consider backporting to 52, but leaving it on the radar just in case.
primary fix still hasn't landed in nightly
Product: Firefox → DevTools
No longer blocks: 1266419
Type: enhancement → defect
Regressed by: 1266419
You need to log in before you can comment on or make changes to this bug.