Closed
Bug 922851
Opened 12 years ago
Closed 12 years ago
Defect - Moving browser to larger secondary display results in clipping / mis-sizing
Categories
(Firefox for Metro Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: sfoster, Assigned: rsilveira)
References
Details
(Whiteboard: [block28] feature=defect c=tbd u=tbd p=3)
Attachments
(2 files)
If you drag the (immersive) browser to a larger (lower dpi?) secondary display, it is not sized or scaled correctly so some of the UI is offscreen. F5 or right-click reportedly corrects the problem. The issue is not present moving from larger to smaller display
Assignee | ||
Comment 1•12 years ago
|
||
Screenshot.
Happening when I move metro browser from the carbon X1 screen (1600x900) to a 1080p monitor.
Updated•12 years ago
|
Blocks: metrov1backlog
Summary: Moving browser to larger secondary display results in clipping / mis-sizing → Defect - Moving browser to larger secondary display results in clipping / mis-sizing
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0
Updated•12 years ago
|
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0 → feature=defect c=tbd u=tbd p=0
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rsilveira
Comment 3•12 years ago
|
||
Hey Rodrigo, can you provide a point value for this defect. Thanks.
Status: NEW → ASSIGNED
Flags: needinfo?(rsilveira)
Priority: -- → P2
QA Contact: jbecerra
Assignee | ||
Comment 4•12 years ago
|
||
I'll need to investigate a bit to figure out the points. I'll update once I have more info.
Comment 5•12 years ago
|
||
Sounds good. Thanks Rodrigo.
Assignee | ||
Comment 6•12 years ago
|
||
Setting points.
Status: ASSIGNED → NEW
Flags: needinfo?(rsilveira)
Priority: P2 → --
Whiteboard: feature=defect c=tbd u=tbd p=0 → feature=defect c=tbd u=tbd p=1
Assignee | ||
Comment 7•12 years ago
|
||
Actually it's fixed now. I still see the black border while I'm dragging the browser, but as soon as I drop it on the monitor screen it looks fine.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
Priority: -- → P2
Comment 8•12 years ago
|
||
Mozilla/5.0 (Windows NT 6.2; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0
I can still reproduce it on latest nightly (build ID: 20131028030205). After releasing the browser on the second monitor, will not go on the entire screen until I change the page I was on.
Assignee | ||
Comment 9•12 years ago
|
||
That's right, it worked for me when I had APZ disabled :(
Resetting the points as it looks like backend issue.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: feature=defect c=tbd u=tbd p=1 → feature=defect c=tbd u=tbd p=0
Updated•12 years ago
|
Updated•12 years ago
|
Whiteboard: feature=defect c=tbd u=tbd p=0 → [triage] feature=defect c=tbd u=tbd p=0
Updated•12 years ago
|
Status: REOPENED → ASSIGNED
Updated•12 years ago
|
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0 → [block28] feature=defect c=tbd u=tbd p=0
Updated•12 years ago
|
Whiteboard: [block28] feature=defect c=tbd u=tbd p=0 → [block28] feature=defect c=tbd u=tbd p=3
Updated•12 years ago
|
Assignee | ||
Comment 10•12 years ago
|
||
I'm not seeing this anymore, very likely bug 937896 fixed it.
Cornel, can you confirm that it's working for you on latest nightly?
Flags: needinfo?(cornel.ionce)
Comment 11•12 years ago
|
||
(In reply to Rodrigo Silveira [:rsilveira] from comment #10)
> I'm not seeing this anymore, very likely bug 937896 fixed it.
>
> Cornel, can you confirm that it's working for you on latest nightly?
Mozilla/5.0 (Windows NT 6.2; rv:28.0) Gecko/20100101 Firefox/28.0
Yes, I can confirm that this is now working on the latest nightly (build ID: 20131121030201).
Flags: needinfo?(cornel.ionce)
![]() |
||
Comment 12•12 years ago
|
||
based on comment 10 and comment 11.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
Comment 13•12 years ago
|
||
Mozilla/5.0 (Windows NT 6.2; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
Verified on latest nightly (Build ID: 20131201030203) during iteration-19 testing and working as expected.
You need to log in
before you can comment on or make changes to this bug.
Description
•