Interface has disappeared in Bing Maps

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Josh Tumath, Unassigned)

Tracking

({regression})

16 Branch
x86_64
All
regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0
Build ID: 20120713030548

Steps to reproduce:

I visited Bing Maps.


Actual results:

In the mapping area, the user interface (zoom buttons, copyright information and a brown bar at the top with options for switching between map and satellite imagery) is not displayed. Also, when zooming in, instead of the image expanding smoothly, the current view shifts to the bottom right corner of the screen until the new images load.

Comment 1

5 years ago
Confirmed in 
http://hg.mozilla.org/mozilla-central/rev/6489be1890c0
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 ID:20120713030548

Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e3c30588f319&tochange=67e09e165ce6

Suspected: Bug 753158
Assignee: nobody → general
Blocks: 753158
Status: UNCONFIRMED → NEW
Component: Untriaged → JavaScript Engine
Ever confirmed: true
Keywords: regression
OS: Windows 7 → All
Product: Firefox → Core
Bug 753158 backed out.
(Reporter)

Comment 3

5 years ago
Part of this bug has been fixed, thanks to the backout, but the strange zooming behaviour is still occurring.

Comment 4

5 years ago
I concur, the zooming is still broken.

Comment 5

5 years ago
Regarding the strange zooming behavior.
I filed new Bug 774169.
Summary: Interface has disappeared and strange zooming behaviour has appeared in Bing Maps → Interface has disappeared in Bing Maps

Updated

5 years ago
Depends on: 774169

Comment 6

5 years ago
This bug was fixed in the re-landing of bug 753158.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Updated

5 years ago
No longer depends on: 774169
You need to log in before you can comment on or make changes to this bug.