Double click does not work for me to unzoom a Plotly plot.
I have tried Firefox, Chrome, Edge and Opera on my Windows 10 PC.
This applies across all Plot.ly demo sites, including R-based ones and Python based ones and others.
It fails 100% of the time.
It also fails from the code I am developing using R both at the distributed version and at ‘4.8.0.9000’.
Yet, double-click works fine for me on sites using other libraries including Dygraph, and also on the following test site: https://unixpapa.com/js/testmouse.html
I know that Plotly double-clock unzoom works for others, so I tried it on an Android phone using the Puffin browser in trackpad mode, which provides a double click capability, and it DOES WORK for me there.
So I know that the basic capability is there. Why exactly it is not working on my PC, I have no idea. It is a Logitech M705 mouse. I tried various Windows mouse speed settings and they made no difference. As I mentioned, double click works ok with other JavaScript libraries and mouse click test sites.
I see that previous reports have been made of timing sensitivity in the double-click detection code. Perhaps my environment just happens to reproduce the problem nicely? If this seems plausible, I would be more than happy to gather any evidence that would be useful.
Any help appreciated.
(I previously posted here: https://community.plot.ly/t/double-click-unzoom-not-working-for-me-at-all/17286)
Related
I'm experiencing black screen in google chrome (and a lot more...read below) after waking windows 10 up from sleep mode.
This issue appears in google chrome and all derived applications, in few words I'm experiencing this in:
Google chrome Version 80.0.3987.149 (pretty sure i was having this issue also before)
The new Microsoft Edge browser based on chromium
All the pwa (progressive web apps) installed with chrome or edge
All electron applications like:
Visual Studio Code
Whatsapp
All the Electron applications made by me.
I had this issue for a long time but the spreading of chrome based services is going to make this thing a lot annoying...
I'm using Windows 10 1909 home 64 bit (pretty sure I was having this issue also in windows 10 1903)
WORKAROUND: if in google chrome (or edge chromium) i keep a tab that in the closing prompts a javascript alert, in the moment when the alert is prompted, the issue is gone, the black screen is gone and i can return to see the whole tabs.
So after waking up windows 10 from sleep mode, if i see black screen in the browser i can just close it with the cross in the top right corner, in that moment the alert is prompted "are you sure to leave this page?", i answer "no i want to stay in this page" and the issue is gone.
Of course this is a workaround cause you can forget to keep that site in the tabs of chrome/edge, and this doesn't resolve the issue in visual studio code.
Starting google-chrome with the --use-gl=desktop seems to work with no side effects.
I had same issue with Fedora, Chrome and NVIDA drivers. At first I tried enbling the vulkan flag.
Go to chrome://flags and enable ignore-gpu-blacklist and enable-vulkan. However, Chrome performance suffers and others have pointed out with this settings.
Found the vulkan tip in a comment here. The use-gl-desktop tip here
I am working on a mobile website at the moment and I refreshed the page, Chrome quit unexpectedly, and since then all touch screen emulation is absent and/or failing.
Chrome Version: 36.0.1985.125 m,
OS: Windows 7 Ultimate SP1
Google Chrome suddenly and unexpectedly stopped emulating devices properly. All touch screen functionality has been disabled and apparently removed. When I emulate a device, the Sensors box fails to be checked and upon inspection, does not show any 'Emulate Touch Screen' option.
I have tried the following, all in conjunction:
Uninstalling/Reinstalling Chrome and deleting all personal settings, including uninstalling all extensions, restoring all defaults, etc.
Restarting the computer
Running anti-virus software
EDIT: Installed Chrome Canary which produced the exact same problem
Please let me know if there are any other relevant details that I might need to add.
Sorry about this. We overhauled the touch emulation in Chrome 36 to be much more accurate (sharing code with what really happens in Chrome Android): https://plus.sandbox.google.com/+RickByers/posts/CBCmhVttj5C. In the process we ended up disabling touch emulation when real touch support was present (at the time we thought this was no big deal because if you've got a real touchscreen why would you want to fake one with mouse?). But some Windows PCs report that they have a touchscreen when in fact they don't really (Eg. Visual Studio installs a touch screen emulator I believe).
We're fixing this at http://crbug.com/395531 - hopefully there will be a Chrome Canary build soon that re-enables touch emulation in these cases.
In the meantime you can mostly work around the issue by disabling Chrome's support for built-in touchscreens at chrome://flags/#touch-events. Make sure you set this back to 'Enabled' after Chrome is updated to fix the issue. With this disabled, some minor aspects of touch emulation (eg. DOM0 ontouchstart= handlers) will not work properly.
Stop the "Tablet PC Input Service" and restart chrome. If chrome thinks you have a touch screen, it won't let you emulate one.
I stumbled across the answer here:
https://github.com/Modernizr/Modernizr/issues/880
This is an HTML 5 Canvas application. It's a pretty standard "designer" application where the user adds objects to a layout, moves them around, and edits their properties.
It works very well, but it turns out to have real performance problems in IE 9 on Windows 7. I would appreciate any thoughts!
Operations often take 10 seconds instead of the usual 2 seconds.
Also, after using the application a little while, the browser gives an error message that the host "is not responding", giving options Recover Webpage and X. Once that starts to happen, it happens for every user action including the File menu, and I can only get out of it by editing the URL location text. In particular, it generally happens on any attempt to use the browser's profiler in Developer Tools. This is obviously frustrating, but it may also be a clue. I wondered if there might be pending synchronous AJAX calls, as suggested by this error message, but capturing the network traffic using Developer Tools suggests that all calls are complete.
The problem seems specific to this combination of browser and OS. IE 9 on Windows Server 2008 behaves OK, and so do Firefox and Chrome on Windows 7. The problem is the same for 32-bit or 64-bit IE.
Most of these operations have a server-side component too. For example, adding a text object makes an AJAX call to serve an image for the object. The server API is implemented as a small TurboGears application which uses ImageMagick for the image processing. But rough profiling indicates that nothing unusual is happening on the server side. This suggests that the problem really is in the JavaScript.
The Task Manager shows the browser using CPU of 90% or more when the application is running. This is true for any browser, not just IE 9. This is likely because of the tight rendering loop in the application, so one idea we had was to redraw the canvas less often. Unfortunately this did not seem to help. requestAnimationFrame seems like a good idea, but is not supported in IE 9.
A colleague suggested that using the Google Chrome Frame plug-in might help. It might be an acceptable solution, but I haven't tried it yet.
I found some advice to turn on the Control Panel option "Use software rendering instead of GPU rendering", but that doesn't seem to help.
One thing I have noticed: It seems the canvas is much slower in IE if you start drawing on it when it's not in the document.
So I do document.body.appendChild(canvasEl) before I draw. You can even make the canvas element dislay: none; but at least it should be in the body.
Update: It seems that for Chrome and Firefox, appending the canvas to the body is slower. So if you don't need it to be added to the body, don't add it for Chrome and Firefox.
I've just realised that on my website, the images look a lot different to what they do on localhost. I'm not sure why, it's baffled me.
Localhost preview: http://d.pr/i/6og
Server preview: http://d.pr/i/OWKx
Localhost gradients: http://d.pr/i/C5el
Server gradients: http://d.pr/i/5pGi
Localhost search bar: http://d.pr/i/YL2X
Server search bar: http://d.pr/i/dTCZ
As you can see they're a lot different. I've literally no idea why, I'm wondering if anybody has had the same problem before?
My website: http://wpvault.com/kahlam/
I don't think there's anything in the CSS that could possibly do this? It's strange, quite stuck with this one. Any help would be much appreciated.
Browser: Google Chrome
The problem is color management in browsers. This isn't a fault with your images at all.
Here is the article that I read.
Here is some excerpts from the article in question:
This specific issue exists because there are two types of ICC profiles, V2 and V4 (all you need to know is that V4 profiles are more accurate; refer to this International Colour Consortium document for the technical specifics).
The trouble is:
Firefox 3.0 and Safari understand ICC V2 and V4 profiles.
Firefox 3.5 introduced a new colour management system which no longer understands ICC V4 profiles (great job guys).
Internet Explorer 8 and Google Chrome don’t understand colour profiles at all!
Edit
I also found this link to blurry images in firefox, this could be related to other browsers as well.
I recently faced a weird issue with Firefox. All the images on my blog were rather blurry as if they were wrongly scaled. So I tried with a new Firefox profile and it worked fine. So there must have been some setting or some add-on that is part of the current user profile that is causing this. I removed all the extensions and add-ons to no avail. Just moments ago, I found the solution on the Blitz Research forum. It turns out to be an issue related to the zoom level for a given website, which Firefox 3.0 remembers. By clicking Ctrl + 0, you reset to the no zoom.
Very strange issue but I have all the images back to normal. It seems when I was uploading them from a 2mb connection it was just uploading them into really rubbish quality images. I got home and uploaded them via my 50mb connection and all was fine - all the images are now back to normal. Thanks for the help.
I have a big problem with my web site (you can see here), several user can't see images with firefox. I use too firefox but I don't have this problem.
These users use firefox 3.5.2 with windows XP or VISTA. I have no idea to find the problem.
Have you any idea ?
Thanks a lot.
Perhaps the user has accidentally blocked images from your domain.
In Firefox:
Tools > Options > Content tab > Load images automatically should be checked > click Exceptions... make sure the Site list does not include mowen-world.com. If it is there, highlight it and click Remove Site.
I've had similar issues a few weeks ago. The reason was that the JPG images were somehow corrupted. Some browsers/OS combinations showed them without problems, but on others they didn't show.
I fixed it by opening every JPG image and saving them again in a good image editor (like Photoshop or Fireworks)
Whenever I get a problem like this, I start from basics... like "is the HTML valid".
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fmorwen-world.com%2F
There are some issues listed here that could cause odd behaviour.
When I look at the site, I can see all the images fine and the website looks reasonably well laid out (Firefox 3.0.14 Windows XP AND Internet Explorer 8 Windows XP).
I can't see an issue using Firefox 3.5.3 on Windows Vista, just FYI.
Personally whenever I have issues with assets not loading or markup/CSS behaving weirdly, my first stop is Firebug. The Net panel shows the requests for any images and their respective responses. Certainly a good place to start looking.