the images in fotorama look crappy in chrome and edge on 1x display, but they are ok in FF. I have tried different settings, but the result is all the same.
Here's the preview http://rgbits.com/dev/houseup/test/test.html#7
I have added a plain image below the gallery for comparison.
I can't find any particular reason for this behaviour, please advice.
Related
Description:
I've checked similar issues, but none of the provided solutions seem to work in this case. My assumption is that this has something to do with pdf document itself, appreciate if anyone could take a look.
Steps to reproduce
Here is the sandbox with the example
https://codesandbox.io/embed/gallant-thunder-x3o7v7?fontsize=14&hidenavigation=1&theme=dark
Expected behavior
Links are clickable. Please see the online demo https://projects.wojtekmaj.pl/react-pdf/
Actual behavior
Links are not clickable
Interesting fact, that google viewer does not open the links either (pages 4, 5), but if you download the document, links are working. I'm using default previewer on MacOS
Environment
React-PDF version: 5.7.2, same behaviour on 4.1.0
React version: 18.0.0, same on 16.4.0
Also, I used iframe and embed, and really it make link clickable but its not display pdf on safari IOS
The problem is you are using a "virtual PDF reader" (GoogleDocs/Mozilla PDF.js) which produces images and searchable text as separate layers, the link is there but it is the highlighted yellow zone not the blue underline text. also due to browser security I have to right click to open at my choice in new tab or new window (my choice would be save link as PDF for offline viewing).
In a true PDF viewer like Chrome embedded PDF Plugin or the users iFrame / offline viewer, the links would work perfectly. Again whichever way the user decides.
Portrait images are rotated when displayed. I found a related issue that was supposedly fixed in github https://github.com/codenameone/CodenameOne/issues/801.
I tried setting
Display.getInstance().setProperty("normalizeImage", "true"); on startup but that did not work on a Samsung Note 5
The code for doing this was removed for some reason, I've reopened the issue to investigate.
Using straight-out-of-the-box lightbox2 (no edits, no mods). It has worked faithfully for the past couple of years since it's been in use. Suddenly noticed the other day that the image no longer fades in/out using Chrome. Image just displays on a new browser page. Works okay on Edge, but not sure about Safari as I've not yet checked that. Is this a Chrome issue? Any fixes?
I had the same problem. Tried many things.
Then I used "lightbox with jquery" javascript that's on their website: http://lokeshdhakar.com/projects/lightbox2
Update: It is not necessary to combine lightbox with jquery. The issue in my case was that I was using jquery older than version 2. If you user 2.0 or above version of Jquery, lightbox will start working again.
I'm using materializecss.com and angularjs for my website. The problem is quite interesting:
When i use Chrome and resize my website, everything stays responsive (not perfectly tough). But when i use the Chrome Emulation tool (with Apple iPhone 6) its not responsive anymore.
Have a look at the screenshots:
So you can see the different scale.
You can have a look at it at zencubes.io
Any ideas?
The description of your problem sounds like it's been answered here previously at Stackoverflow here, where it works in the device emulator in Chrome but not on the actual device itself.
Why CSS Media Query doesn't work on mobile device but yes on Google Chrome device emulator?
Have you checked your Viewport meta tag settings, in particular the width attribute?
Having very inconsistent results in viewing PDFs on the iPad Air (ios 7.1.1). Memory consumption and CPU usage doesn't seem to be an issue. Getting black boxes and sometimes app crashes when viewing PDFs. Also it doesn't happen on the iOS simulator, but only the actual iPad.
Heres some screen shots.
This is how I'm opening the PDFs (using angular):
$scope.openPDF = function(pdfName) {
var ref = window.open('img/pdfs/' + pdfName + '.pdf', '_blank', 'location=no');
};
Also, it seems like others are experiencing this problem.
https://discussions.apple.com/message/24129741#24129741
https://discussions.apple.com/message/23480067#23480067
Any direction would be much appreciated.
EDIT: This is still an issue. inAppBrowser does not fully garbage collect memory on PDFs
Apparently this is related to an HTML5 Video memory leak bug.
inAppBrowser does not do garbage collection properly if an video tag exists on the page. Ended up removing the tags and everything seems to be working properly.
I also ended up using an inAppBrowser Extension plugin for some of the extra options, it seems like all the options from the official plugin are still supported which is nice.
I initially filed a ticket and closed it.
This is the thread where the HTML5 Video tag leak is discussed.
From my research I cam to the same conclusion as #ChristopherMarshell that it is to do with a HTML5 video tag memory leak. Instead of using inAppBrowser to do the PDF document you could use Google docs, similar to:
window.open('https://docs.google.com/viewer?url=http://www.example.com/test.pdf&embedded=true', '_blank', 'location=yes');
This opens the PDF in Google docs and you shouldn't get any black boxes :)