I am using pdf.js in my web application and it works fine until I updated chrome to Version 30.0.1599.69 m this morning.
The PDF is rendered with wrong character. Zooming in or out may correct the character but it doesn't work to all document. Different document may be 'corrected' with different zoom scale.
Sometime zooming doesn't fix the problem.
Does anyone facing the same problem? Any solution?
Screen capture:
Temporary solution is to fix users' chrome version to version 29. This is the most practical solution in our case for the time being.
Related
I am taking webpage screenshot of svg content using canvg. In Chrome, Opera and IE11 it seems to work fine, however in Edge browser it only weirdly renders black background with no content on the canvas.
Try it here in Edge browser
Open the link above and try the following examples
1) soccer
2) floorplan
I am unable to find the problem. Apparently looks like Edge is not supported by canvg. I hope someone already found a solution for this. It will be a great help!
There's more information about this issue here: https://github.com/canvg/canvg/issues/520
There is currently a merged PR that has not been released as mentioned in the issue and there's a workaround by monkey patching the code from that fix into the canvg code. You may want to subscribe to that issue so you know when the patch is released.
I had a hard time figuring a proper title for this question..
I am loading PNG files from external URL, but with one particular PNG, no-power-of-two, alpha-chanel, created with gimp, when I loaded and use as texture in a plane, It renders mixed with what it looks like screenshots portions of the current screen. in the attached screenshot you will see that it looks like if the cat had a layer on top with inverted parts of the chromium developer inspector window, that is opened at the right.
I notice that it says that as the image is not power of two, has to be resized, but I had not noticed that behavior with other textures.
using three.js R77, Chromium Version 57.0.2987.98 Built on Ubuntu , running on Ubuntu 16.04 (64-bit)
Yikes, that's a bug in the browser. Could you please post a self-contained sample showing the problem? If it's not too much trouble please create a bug on crbug.com/ and attach it, but otherwise please just put the test case somewhere and send me a link. Thanks. (I work on Chrome's WebGL implementation.)
Chrome browser crashes ("Aw Snap!") randomly when rendering Ext JS Donut Charts.
I initially thought this was a data issue. But, I was able to reproduce it even on Ext JS Kitchen sink (http://examples.sencha.com/extjs/6.0.2/examples/kitchensink/?charts=true#pie-donut)
To reproduce this just check and un-check the boxes on Legend below the donut chart. which will cause the chart to re-render and eventually crash (it sometimes takes me 20,30+ clicks to reproduce this).
This issue is limited to Chrome Browser only.
I've found few threads describing the same issue
Link1
Link2
But, No solution yet.
I need help finding a workaround or solution.
Thanks in advance.
This is known Chrome issue. Should be fixed with Chrome 55 which was released couple of days ago.
You can see the Chromium ticket here: https://bugs.chromium.org/p/chromium/issues/detail?id=666046
Testing: I have app which uses Ext 6.2 charts interactions a lot. It used to crash in couple of seconds - with version 55 so far no crash! :)
I am trying to build a map-based web app using mapbox and leaflet.js.
I am loading around 300 markers into a featureLayer from a geoJSON file. This seems to work beautifully in every browser except internet explorer, which freezes for a good 10 seconds or so every time markers are loaded or filtered using featureLayer.setFilter. I have uploaded a demo of this here.
Locking at the IE performance analysis the culprit seems to be the 'addDoubleTapListener'. This seems to be a known issue (https://github.com/Leaflet/Leaflet/issues/4357), and the solutions suggest rolling back to leaflet 0.7.5, or using the 0.7.7.1 branch (which has a fix that reverts touch detection). I have tried both, and neither seem to have any effect on the issue. Upgrading to the leaflet 1.0.0-beta is also suggested, but this doesn't seem to be compatible with the current mapbox...
Any help with overcoming this issue would be much appreciated.
Ok the solution I found was to remove the following lines from leaflet-src.js 0.7.7.1:
if (L.Browser.touch && (type === 'dblclick') && this.addDoubleTapListener) {
this.addDoubleTapListener(obj, handler, id);
}
IE now loads the markers lightning fast and all of the functions appear to still be working in all the devices I tried. Not an ideal solution, but will serve as a stop-gap solution until Mapbox supports Leaflet 1.0.0.
I have a problem with image quality in Firefox: Firefox seems
to zoom "everything" per default so some images really look
fuzzy while in chrome their quality is perfect!
I found out, that there is a setting in Firefox, which resolves the problem:
"View->Zoom->Zoom Text only".
Do you know a way to force Firefox to use this setting for a special
website (using javascript)??
Thanks a lot
Bye
No, because that's a setting for users, who may have poor eyesight and want to actually see the images on your site. It's not for you to make that decision on their behalf.