Closed Bug 781449 Opened 12 years ago Closed 8 years ago

Google Docs Viewer is not working in embedded mode in Nightly 17.0a1. It was working fine in standard Firefox 14.0

Categories

(Firefox :: General, defect)

17 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dkh.hyd, Unassigned)

Details

(Keywords: regression, Whiteboard: [closeme 2016-04-10])

      No description provided.
Keywords: regression
Priority: -- → P3
WFM with your link on FF14/FF17.

Could you test with a new profile and your Nightly?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Severity: major → normal
Priority: P3 → --
It is working with a newly installed Nightly. But not working on Windows.
If it is the profile fault, then why will it work on Firefox-14 but not on Nightly-17 which share the same profile?
In general, it's better to test Nightly (FF17 here) with a different profile than the current one with the stable release (FF14).

Which error do you see with FF17 and Google Docs Viewer? Make a screenshot if you want.
Firefox: 45.0,Build ID: 20160303134406
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0

Hi Deekshith,

I have tested this issue on the latest Firefox (45.0) release, latest Nightly (48.0a1 - 20160308030418) build and I could not reproduce it. The Google Docs Viewer works properly. 

Can you please test this on the latest Firefox release or latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). 

Thanks,
Cosmin.
Flags: needinfo?(dkh.hyd)
Whiteboard: [closeme 2016-04-10]
This is no longer an issue. It works well. I believe, I have reported it very long back. It is well on all current versions now. Tested on Firefox 45, Firefox 46 Developer Edition.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(dkh.hyd)
Resolution: --- → INVALID
Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.