According to the bug tracker, this should be fixed: https://code.google.com/p/earth-api-samples/issues/detail?id=108
My code in the mouseup handler for a Google Earth object:
setTimeout(_.bind(function(){
$('#takecontrol').focus();
this.googleEarthObj.getWindow().blur();
}, this), 1);
This works in Firefox, but it doesn't appear to be working properly in Chrome. Has anyone found a workaround?
Related
Summary:
I want to develop similar extension to LocationBar2 that was available on Firefox, before WebExtensions (WE) came along.
Basically on hover, to simply underline parts of url, nothing more nothing less.
The problem is that this kind of API is not available in Firefox or is privileged.
Then, I stumbled upon Firefox Experiments at
https://firefox-source-docs.mozilla.org/browser/urlbar/experiments.html#developing-address-bar-extensions
Also, found that (I think) this file has the following properties and methods needed to modify:
https://searchfox.org/mozilla-central/source/browser/components/urlbar/UrlbarValueFormatter.jsm
Can anyone point out is this even possible? Not to waste a few days banging my head around it.
Thanks.
The specific warning message is:
Unable to preventDefault inside passive event listener due to target being treated as passive.
This issue can also be reproduced easily in the demo site by JTSage if you use chrome F12 "Device" mode -- many warning in F12 console.
http://dev.jtsage.com/DateBox/jqm/timeflipbox/
http://dev.jtsage.com/DateBox/
Is it something to be concerned about? Occasionally my Chrome simulator would freeze. But I do not know for sure if this is related to those warnings.
I have also googled a bit to find below link, but I do not know enough on how to apply their suggestions on jtsage timeflipbox yet:
https://github.com/bevacqua/dragula/issues/468
Any suggestions?
Use this CSS:
.ui-datebox-container {
touch-action: none;
}
Reference: https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action
I have installed fresh Arch Linux with linux-ck and awesomewm. After that I have installed google-chrome and started it. Everything works well, but if I open other application (chrome lose focus) and then got back to the chrome, it freezes. Mouse cursor works as expected (cursor changes after hovering link, input field, etc) but view is not updated.
Everything works well again if I change desktop to the second and go back to the first again (mod+2, mod+1). Chrome works, responses etc well.
I bet this issue has something in common with hardware acceleration. If I run some game (steam), lose focus, get back to the game - it shows last rendered screen before focus has been lost (sound is ok, game is responsible but does not update screen).
I use nvidia. Do I need some extra configuration to handle it ?
You want to disable "Use hardware acceleration when available" in Chrome settings.
For me, disabling hardware acceleration as Alex pointed out solved the issue. This bug has been brought forward before in awesome's issues GitHub page.
Apparently, the problem is not awesome. Graphics drivers might be involved but the main suspect seems to be the compositing manager. Running awesome with the "--no-argb" flag and disabling the comp manager seems to solve the problem.
The problem was xcompmgr which caused "freezing" view. I switched it to unagi and all of the problems have gone.
This is an issue I've been experiencing only for the last few days; when following a link to jsfiddle, or even going to the jsfiddle homepage (on IOS 6, iPad 2), jsfiddle doesn't initialise properly, and all I see is "initialising the awesome". Even logging in and creating a fiddle doesn't work. The issue only seems to have appeared since some recent downtime which I assume they were updating jsfiddle during it. Has anyone else experienced this issue/have a fix?
NB: this occurs on both safari and chrome.
Alright, I've sent an email to jsfiddle support, and I came up with this response:
We're working on that.
https://github.com/jsfiddle/jsfiddle-issues/issues/330
For the moment please use draft feature or add /embedded/result to the
URL.
http://doc.jsfiddle.net/basic/introduction.html#draft-page
Regards, Piotr
Hopefully this means that the issue will be fixed soon, however, in the meantime, use: (for example)
http://jsfiddle.net/ (your fiddle)/embedded/result
I.e, just add /embedded/result to the end of the url as Piotr suggested.
I can't get IE to print my canvas (generated using excanvas)... I'm using the most recent version of excanvas.
http://dl.dropbox.com/u/997831/canvas.html
(Note: I already tried having the canvas element already on the page instead of creating it with document.createElement)
Unfortunately, there is no good answer here. There has been a ticket open for well over a year regarding the printing of excanvas that has yet to be answered. You could try the silverlight version of excanvas it's a little better but still suffers from similar problems.
The only way to get it printed properly now would be doing a print screen and then printing the image. Unless an newer version of excanvas comes out or IE9 is released, native printing on IE just isn't going to work.
my best shot currently is printing pre-rendered image
(see wkhtmltoimage on google code)