We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

Ketju on suljettu ja arkistoitu. Esitä kysymys, jos tarvitset apua.

PDF.js will not property display large maps (from ESRI mapping products).

  • 3 vastausta
  • 1 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja Andrew

aureolin
aureolin
more options

Test PDF at: http://www.sloplanning.org/gis/mapimagepdf/RuralCDMaps/Rural%20South%20County%20CD.pdf

The PDF downloads VERY slowly (more than 2 minutes on a fast connection) in Firefox, but only seconds in Chrome or IE. When the PDF is rendered, most of the graphic elements within the PDF are missing; comparing the PDF image between FF and Chrome is stark. A good test is to wait through the long download in FF, then press the 'download' button and compare the resulting image displays. The 'downloaded' version has the graphics that are missing from the in-browser display.

At the moment we're stuck telling our clientele to not use FF. :(

In my testing, this is occurring in v27.0.1 of FF on Windows 7; I'm not certain of all the configurations for our clientele where this is also occurring.

Thanks, Steve

Test PDF at: http://www.sloplanning.org/gis/mapimagepdf/RuralCDMaps/Rural%20South%20County%20CD.pdf The PDF downloads VERY slowly (more than 2 minutes on a fast connection) in Firefox, but only seconds in Chrome or IE. When the PDF is rendered, most of the graphic elements within the PDF are missing; comparing the PDF image between FF and Chrome is stark. A good test is to wait through the long download in FF, then press the 'download' button and compare the resulting image displays. The 'downloaded' version has the graphics that are missing from the in-browser display. At the moment we're stuck telling our clientele to not use FF. :( In my testing, this is occurring in v27.0.1 of FF on Windows 7; I'm not certain of all the configurations for our clientele where this is also occurring. Thanks, Steve

Valittu ratkaisu

Hi Steve,

I have filed a bug for this issue.

I can currently running our beta version (29) on Windows 7 and I can reproduce your issue.

I can't think of a reason why this is happening so I filed a bug but if somebody comes along and knows why, then we can figure it out then.

Thanks!

Lue tämä vastaus kontekstissaan 👍 1

Kaikki vastaukset (3)

Andrew
Andrew
  • Moderator
more options

Valittu ratkaisu

Hi Steve,

I have filed a bug for this issue.

I can currently running our beta version (29) on Windows 7 and I can reproduce your issue.

I can't think of a reason why this is happening so I filed a bug but if somebody comes along and knows why, then we can figure it out then.

Thanks!

guigs
guigs
more options

Looks like this is a p3, please keep track of this issue further in this bug. If there are any other questions in the future, we are happy to help.

Andrew
Andrew
  • Moderator
more options

This seems to be fixed now. Thanks for reporting.