Closed Bug 1351901 Opened 8 years ago Closed 7 years ago

Exporting Google Docs file as PDF adds two blank pages at the end of the document

Categories

(Web Compatibility :: Site Reports, defect)

Firefox 52
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: laan.indrek, Unassigned)

Details

(Keywords: regressionwindow-wanted)

Attachments

(1 file)

Attached image FirefoxVsGoogleDocs.png
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170323105023 Steps to reproduce: 1. Open Mozilla Firefox browser (currently up to date version 52.0.2 (32-bit)) 2. Log in to Google account 3. Go to Google documents 4. Create a new empty Google Docs document 5. Do nothing or type in any amount of text and/or add content 6. Go to File menu 7.1. select Print Preview and review the page count of the document 7.2. select Download as... > PDF and review the page count of the created document Actual results: 2 additional blank pages are visible in Print preview and created PDF document although original document did not display them in document editing mode. This does not occur for the same document in, e.g. Internet Explorer 11. NOTE: No page breaks, etc. hidden formatting used, just plain text, Paper format Letter or A4, portrait, margins 1in/2.54cm for each side. Issue started between 03/14/2017 and 03/20/2017. Expected results: Document is displayed/exported to PDF in correct length without blank pages at the end.
Note: I have confirmed bug on 3 separate workstations (Win 8.1 Pro, Win 10 Pro, Win 10 Pro; all 64-bit).
I tested with a blank document, I can't reproduce it with FF52 on Win 7 64b. Both print preview (in GG Docs) and download as PDF display only 1 page. Did you test with a fresh profile? https://support.mozilla.org/t5/Install-and-Update/Use-the-Profile-Manager-to-create-and-remove-Firefox-profiles/ta-p/2914
Flags: needinfo?(laan.indrek)
I retested on a clean virtual machine (Win 10 64bit), installed clean copy of latest FF and can confirm the problem still exists, so it is not related to Firefox profile.
Flags: needinfo?(laan.indrek)
Could you test with Nightly in your VM, please: https://www.mozilla.org/en-US/firefox/nightly/all/
Issue appears in Nightly as well. Tested on same VM with 54.0a2 (2017-03-30) (32-bit). Don't know whether earlier FF52 installation has any effect on it. Since already at it, I tested on Linux Mint 18.1 VM with 51.0.1 (64-bit) Mozilla Firefox for Linux Mint, mint - 1.0, and the problem appears there as well. Starting to suspect Google is somehow behind it.
Hmm, issue did not appear in Internet Explorer, but does appear in Chrome, so it is definitely not a FF issue.
As you are able to reproduce the issue on various machines, could you download the tool mozregression to narrow down a regression range. See http://mozilla.github.io/mozregression/ for details. Run the command "mozregression --good=51" then for each build launched, make the test and enter if it's good or bad. After the run, copy here the final pushlog from the repo mozilla-inbound.
Flags: needinfo?(laan.indrek)
Turns out, the only constant is my Google account. Tested with another account and the problem does not appear. Some weird fault in my Google account, so it seems. I'll take it up with Google. Please close this bug report. Thank you very much for your support and patience!
Flags: needinfo?(laan.indrek)
This is weird, maybe a bad pref in your Google account. Don't hesitate to post when you get the answer.
Component: Untriaged → Desktop
Product: Firefox → Tech Evangelism
Version: 52 Branch → Firefox 52
I'm guessing we can close this report now. If anyone has more information, please open back up.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: