Until a day or so ago, the Canvas2Image JS library and .toDataURI JS method worked in Chrome. http://www.nihilogic.dk/labs/canvas2image/ Now, with Chrome version 19.0.1084.46, if you try clicking Save PNG on the referenced page to download a PNG version of the HTML5 canvas element, it doesn't prompt a download - but generates a MIME type error. Is this intentional - perhaps for security reasons, or a bug? (It continues to work in Firefox.)
It's a bug in Google Chrome v19 as it works fine in v18 and v20. I'm sure it'll be fixed soon.
Related
I used this nifty feature that chrome had for quite a while called "canvas inspector". It was an experimental dev feature that had to manually be enabled.
It was quite helpful when working with webgl via something like THREE.js where you can easily create a bunch of undesired draw calls by accident.
Also, it worked on any website, you could simply take a snapshot and see whats going on in the canvas.
It... miraculously disappeared one day, and google does not give any insight.
I've tried some extensions but they dont feel nearly as good, or i couldn't even get them to work. Is there another way to get this back into chrome?
Apparently it was doing some cheeky stuff that they didn't want in the main project so it was removed in this issue: DevTools: make Canvas profiler an extension
We can make it an extension though. This bug is for tracking removal of the canvas profiler from the DevTools. There will be a separate initiative of porting the code being removed into github and publishing it as a Chrome extension.
According to that issue they might move it to an extension in the future but I haven't found any traces of it as of now. They haven't responded to a question in the above issue about where the new issue could be tracked.
Chrome and Firefox have both removed their Canvas inspectors...
Original Answer:
This is not exactly what the question asks for, but Firefox has a canvas inspector integrated:
https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-developer-tools/
You can enable it in the settings of the normal inspector
EDIT: (2019)
The Canvas Inspector has been removed as of Firefox 67:
Mozilla deprecated listing
Bug report with reasoning
Alternative:
spector.js - Recommended alternative by Mozilla
Canvas inspection was just removed!
You can download an old version of Chromium here like Chromium_OSX_43.0.2357.81.dmg. (Provided by freesmug)
Happy Canvas Inspection!
This is the best extension inspector I’ve seen so far.
https://spector.babylonjs.com
First go into
chrome://flags
Then enable
Developer Tools experiments
Then after restarting your browser, open the devlopers tools by hitting f12, then in the top right corner is a gear. Click on it, go to experiments, then find "canvas inspection". It's unstable, but usable.
I've been using jplayer jukebox for some time with no problems but it has suddenly stopped working in Chrome. Still works fine in IE and Firefox but the playlist no longer shows in Chrome. It was definitely working at the end of June 2014 when I last added a track. webpage is http://www.jonphilibert.com/gallery.htm
Any suggestions gratefully received
Hilary
Try changing the "mp3" to "M4A".
https://groups.google.com/forum/#!topic/jplayer/Lyk7Znv1pWE
What has happened is that this Chromium issue means that Chrome uses Flash for playback since Chrome 36, rather than HTML5.
Your problem is that the path to the SWF path is set up incorrectly - Chrome Console tells me "GET http://www.jonphilibert.com/Jplayer.swf 404 (Not Found)"
So once you configure the player to have the correct SWF file path, playback should start working again in Chrome.
Note this means that playback also won't be working in other browsers that don't support HTML5 audio.
Our team uses Chrome Web Developer tools to debug JavaScript. As of yesterday when our browsers upgraded to Chrome Version 27.0.1453.93, the Sources section no longer lists all the JavaScript files. Does anyone know if this is a bug or if there is a setting? Some JavaScript files are still listed but I can't find the criteria for files being listed or not. I checked on an older Chrome Browser pointing to the same URL and all the files are listed. Anyone solved this?
I guess you may have some javascript code that has been loaded dynamically. If it is the case, you should use the phrase
//# sourceURL=foo.js
at the beginning of your javascript code. foo.js will be assigned it by debugger. And debugger will show it with that name.
chrome and firebug accept it, I am not sure about other browsers
If you try to visit the default rss feed for any recently updated wordpress site in the chrome browser you ALWAYS get this annoying prompt for "Which service should be used for viewing?". This did not used to happen in chrome. This does not happen in other major browsers. How can I correct this in chrome to just show me the parsed xml like it used to?
PS the example page you see in the background is http://wordpress.com/feed - as soon as you try to visit that page in chrome you should see this prompt as well.
I just discovered "Feed Intent Viewer" which is a Chrome extension that basically brings back the old functionality.
https://chrome.google.com/webstore/detail/oceapojkdgeophkjdijkpbjifdnfimdh
I am using chrome Version 21.0.1180.79 on ubuntu and having the same request to download issue on such safe websites as sciencefriday.com. I have submitted the problem to chrome. -fingers crossed for a patch-
I found a solution after many research (because it's really annoying...)
Download and install the new Beta version of chrome: it's all fixed
it is a problem of "same origin policy" on local file, i have tried that
C:\somewhere some folder\chrome.exe" --allow-file-access-from-files
don't work, now i am working javascript on localhost(web server) ...my situation is ridiculous, it make the "iframe loading" and xmlhttprequest(which not work for local files) have no difference for scripting.
Does chromium just the same function as chrome except "--allow-file-access-from-files" works? if not , writing code for ie,chrome,chromium just create one more issue but solve one.
--allow-file-access-from-files works for me on Chromium under Ubuntu. However, you have to close Chromium completely before this, because otherwise it will just open a tab in the existing Chromium process (which was presumably not started with that option).
Otherwise, this is just bug 40787.