Display issues with SVG viewer on Google Drive - google-drive-api

I'm using the Google Drive API (which is awesome!) to upload SVG content. The main problem I have is that the labels on the SVG are displayed incorrectly when I open the file in Google Drive. They appear much larger than they should.
Downloading the file and opening in Chrome looks fine. I believe the same issue happens in Gmail preview.
Here is an example SVG file: https://docs.google.com/open?id=0B16Q4tqg5T6QcDRzTE1LSmxMTE0

The issue seems with the viewer and not due to the upload mechanism. Have you tried uploading the same file from the Drive UI? Do you get the same rendering issue?

The preview still misbehaves and completely garbles the SVG when the google drive renders it. As reported earlier it is ok when downloaded and viewed locally with Chrome. (I also like to get this fixed).

Related

Why does Google Chrome only displays the first page a pdf file?

I'm facing a problem with Google Chrome. One of my PDF only shows the first page and the rest looks as following:
Example:
First page is displayed normaly.
It recognizes the amount of pages in the PDF.
If I download the PDF, it is completely fine and useable, I even can open it in Chrome and it works fine. The problem doesn't occur on Firefox or Safari.
I'm using Google Chrome Version 85.0.4183.83 (Official Build) (64-bit)
Thanks for your help.
I experienced the same issue (but with another website). After investigation, it appears that this has something to do with SameSite cookies.
You can fix it by setting this flag to Disabled then restart Chrome:
chrome://flags/#same-site-by-default-cookies
Update: Found an issue in the Chromium bug tracker related to this problem:
https://bugs.chromium.org/p/chromium/issues/detail?id=961617
This issue appears to be caused by a conflict between Chrome and Fast Web View pdf optimisation. To fix it you need to turn off the optimisation within your pdf program settings and save the file again (in Adobe products this is located Preferences>Documents>Save Settings - uncheck Save As optimizes for Fast Web View). Pdf files which don't include this optimisation render all pages correctly.

Embedded PDF Issue in Edge Browser

When using the Microsoft Edge browser, by default when you open a PDF it will open the PDF in a new tab using the built-in PDF viewer. To avoid this, you can adjust the browser's settings: Toggle on the "Always open PDF files externally" option. This works great. However, it presents a separate issue. Our internal applications use embedded PDFs in iframes. When the external toggle is set to on, these PDFs will not show in the iframes. This doesn't happen in Chrome. Has anyone else experienced this and know a work around?
I've tried removing the type="application/pdf" from the iframe tag to no avail. I can't find anything else online.
It looks like an expected result because you have enabled the option Always open PDF files externally.
So MS Edge browser is giving you an option to download the PDF file and open it using the desired app.
You said this doesn't happen in Chrome browser.
If you enabled the Download PDF files instead of automatically opening them in Chrome option then you will notice the same result in the Chrome browser.
Output in the Chrome browser:
If you click on the Open button then it will download the PDF file.
I did not get any solution or a workaround for this issue.
If you think that there should be an option to load the file in an iframe if Always open PDF files externally option is enabled then I suggest you click on the Send Feedback button in the MS Edge browser and try to provide your feedback about it to the Microsoft.
I posted feedback suggesting that an exclusion/inclusion list be in included but the simplest way would be to treat the frame as part of the session. But this is not Microsoft it is the Chrome projects issue.

Unable to copy SVG images from Wiki to Google Docs

I've tried to copy a rich text with formulas from here, but it isn't working. Google docs says "Unable to create some images", and Word 2016 just say nothing. My OS is Windows 10. I've tried different browsers (Chrome, Opera, Edge).
Google Docs wont accept pasted svg images. A work around (if you have control over your mathjax plugin) is generating those images as .png.

Issues on chrome showing an embedded PDF

I have the following code in a html document:
<p>PDF sample</p>
<object data="http://www.whateverdomain.com/whatever/~/media/sample.pdf" type="application/pdf"></object>
This is working in IE, Firefox but not in Chrome. Appears a grey box in the browser with no embedded pdf. When I check on "network" tab in chrome I'm receiving a HTTP 200 response but PDF is not shown.
I tried URL encode tilde "~" symbol replacing it by %7e but still its not working on Chrome.
I don't have the possibility of changing the url which is provided by an external service.
Do you have any clue on how to solve ?
You might wish to try and use a simple iframe. At the very least I am pretty sure that works for chrome, might not work for IE though. Another alternative is using the Google Docs viewer, with that you are sure to be cross browser compatible, although some pdf's might not render perfectly. The last option you have is using something like pdf.js to render the pdf's yourself inside the browser. Gives you a lot of control and ensures that even people running computers without a pdf viewer installed (or a native pdf viewer like chrome and firefox) will be able to view the file.

Use Adobe reader instead of chrome pdf viewer to display a pdf

I'm outputting a pdf which has been made with scribus, and in all browsers except for chrome it outputs fine, however with chrome the letters are cut off and lower than usual. I found that disabling the chrome pdf viewer fixes the issue locally. But what about users who do not have it disabled? Is there some way I can make adobe reader show it instead of the chrome pdf viewer in my code?
Any help is appreciated,
Thanks
Edit: I can't make the user download the pdf as it is somewhat a preview before they send it in.
One option would be to use a Content-Disposition header to force the PDF to download as an attachment. When the user clicked on the downloaded file, it would then open in their registered PDF viewer rather than in Chrome.
I ended up flattening the pdf using the flatten option, it unified the result accross all browsers.