I seemed to have found a bug when selecting dates running Chrome with HandsOnTable versions later than 15.1.
I'm able to drop down the calendar but I'm unable to select a day within the calendar control. This is only a problem for me in Chrome as it seems to work fine in Firefox, IE and Edge.
After further research this bug only occurs on a touchscreen enabled device but the user is using a mouse.
Here is a screen capture video of the behavior straight from www.handsontable.com website:
https://www.youtube.com/watch?v=CEdiWQ5R5Es
GitHub Issue Thread: https://github.com/handsontable/handsontable/issues/2812
Let me know if anyone else can reproduce this behavior and if there is workaround.
I just had the same issue. Maybe this can help you. I did for me.
Currently I'm working with handsontable.full.js (version 0.18.0) and
I changed line 24550
addEvent(self.el, 'ontouchend' in document ? 'touchend' : 'mousedown', self._onMouseDown, true);
to
addEvent(self.el, 'mousedown', self._onMouseDown, true);
I took it from
https://github.com/dbushell/Pikaday/issues/276
Hope that helps.
Good luck
This is actually a better solution in my opinion. This will register both events separately so these events will work on all devices.
https://github.com/dbushell/Pikaday/issues/374
Thanks for the step in the right direction. Hopefully Pickaday and HandsOnTable can incorporate the change soon.
Related
I am working on an angular project and have developed an application which needs to be compatible with iPad the problem is in with radio button whenever it is clicked it freezes/disabled in Safari and works fine every where else in chrome Mozilla etc . I was looking for a suggestion which can help me solve this bug thanks in advance
We can't judge if we don't see the code. But generally speaking in those kind of problems, there's some functions that are not supported by some browsers.
So either you gotta find an equivalent function supported by all targeted's browsers, or rewrite the code in an another manner.
EDIT: The symptoms of this problem are inconsistent. Today I tried this again and suddenly it works... sometimes. If I refresh over and over it works about half of the time. If it runs inside an iframe the iframe requires both allow-same-origin and allow-scripts. I can't really be sure about any of this though because it is so inconsistent. Ultimately I decided to go with IP based geolocation simply to avoid the headache.
If anyone can replicate this problem, let me know in the comments.
TLDR: This link will display an error in safari and ie11, but not chrome.
The code in question:
<!DOCTYPE html>
<html>
<head>
<script>
navigator.geolocation.getCurrentPosition(function(position){
document.body.innerHTML = position.coords.latitude;
}, function(error){
document.body.innerHTML = error.message;
});
</script>
</head>
<body>
</body>
</html>
The problem: On chrome, edge beta (so basically chrome) and chrome on android, this code will succeed and print your devices latitude to the page.
On Safari, safari for ios, and IE11, this will fail with the message "This site does not have permission to use the Geolocation API."
I assume it's not referring to the user granting permission to access location data, but i checked this anyway. Doesn't appear to be the case because it's working in one browser but not another on the same device. In my example, it works in chrome but not ie11 on the same windows 10 computer. I also had a coworker confirm the same thing, it works in chrome but not safari on his mac.
That leaves me thinking it's a domain issue, but why would it work in one browser and not another? After tons of Googling the best answer I can find is that it is an SSL issue, but if you go to https://developers.google.com/maps/documentation/javascript/geolocation you can see that even google.com is facing the same issue. So I think that rules that out. you can even try it on w3schools own site https://www.w3schools.com/html/html5_geolocation.asp
Google of course has no input here because navigator is a product of html5
I can't reproduce the issue in IE 11. I tested the Google and w3schools links in IE 11 and they asked for permissions to get location and can show the location if I permitted. I also tried the code snippet you providing and it output the position in both IE 11 and Chrome.
Have you unchecked the "Never allow websites to request your physical location" box in IE 11? Besides, I also found a similar thread and you could also refer to the solution in it.
And in your post, it seems that you have found a solution. I suggest that you could also put your solution as an answer and take the best answer as an accepted answer. It can help other community members in future in similar kind of issues.
Recently a Chrome extension our company uses was reported to be causing extreme slow down in the UI when in use. Ive been trying to find the cause of this issue.
After a week or two I have narrowed it down to the canvas's drawImage method.
Initial thought was that this method was holding onto the thread for too long.
This extension works great up to Chrome V43 (couldn't find chrome V44 anyway). With the current version 45, it causes heavy delay on UI response. Seems like a chrome bug.
Googling around I found this https://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=490478
I am not sure if this is exactly the issue I am running into with drawImage but taking the suggestion from someone who posted there, I went into chrome://flags/ and disabled "Disable accelerated 2D canvas".
This instantly solved the issue & the extension is actually working better than ever before. The question is why? and how can this be used to make a temporary fix to the code since it'd be unreasonable to just ask everyone to disable this flag.
Recently updated my Google Chrome to version 32.0.1700.76 m and it looks like tooltips have stopped appearing over html elements with the 'title' attribute set.
<span alt="Testing" title="Testing">hhh</span>
Here is an example jsFiddle:
http://jsfiddle.net/ricksuggs/cDhEL/
I thought it was an HTML standard, it is still working in Firefox, anyone else experiencing the issue?
Version 32.0.1700.76 m works fine for me. Have you tried just clearing your Chrome browser cache to make sure it's not a caching issue?
Unfortunately, this is an old bug that have pop with version 32.0.1700 and is still present in v55 on some system such as mine too.
If you encounter this bug. Please go to http://download1.srware.net/old/iron/win/portable to test version 31 then 32. If you find out it works with v31 but it doesn't with v32, please report it in the chromium bug tracker issue. Specify your setup sharing a link provided by DriversCloud.com to help dev to fix it. They need feedback and details.
I've just updated Chrome from 17 to 18.0.1025.142 and got all the ExtJS charts crashed in the web-site. The same issue reproduces on the Sencha example. Try clicking "Reload data". Any ideas?
I've come across the same problem. It looks like it's a bug in that version of chrome as the dev stream (v19) fixes the problem. It's a total PITA, but hopefully v18 won't be the current version for long. We just disabled the charts for that browser until it's sorted.
Here is an issue opened with chromium. Log in and star the issue so that it goes up in priority for chrome developers.
Also look at this thread for a workaround. Didn't work in my scenario but it might help you.
http://www.sencha.com/forum/showthread.php?192175-4.0.7-Line-Charts-Broken-in-Chrome-18-Mac-(and-also-it-appears-windows)