I have been working on this bug for a while now , for some reason the drag and drop uploading I implemented on my site has not been working in chrome. No error messages or anything. Just when you try to drag a file over the designated area you get the mouse icon of the circle with the line through it. So after testing and testing and testing I came to realize that even if I go to the html5 Official demo page for the drag and drop it does not work there either in Google Chrome.
Has anyone ran into this? is there some type of security setting that got triggered in my Chrome browser that is preventing the drag-n-drop ?? I am concerned now that there may be other user that may run into this. Currently I check if the user's browser if HTML5 compatable and then only offer the drag-n-drop option, if not I fall back to the choose a file button. But now I'm learning that there may be a third case - which is mine now . I have the newest version of Chrome , but it just for some reason started blocking drag-n-drop a few days ago. It used to work just fine.
EDIT
the HTML5 drag-n-drop demo site
and I'm using Chrome Version 39.0.2171.65 m
I found strangely enough (on version 57.0.2987.110) that closing all instances of chrome, opening task manager and making sure it is fully closed, then restarting it seemed to get the dropping working again.
I'm not sure of a fix when this is occurring but I did see a bug report about this at https://productforums.google.com/forum/#!topic/gmail/RgPdExhVPMs but it looks to me like a browser update (as this was originally posted in 2015 and likely isn't a problem anymore) would fix it right up.
Related
Good evening, I come to you because recently my autocomplete on vscode (especially in javascript) does not work anymore, I have another PC with the same version of it so I made a copy of the files on my other PC but still nothing. I also tried to completely reinstall vscode but still nothing
Any idea ?
Hiļ¼here is my suggestion.
You can enter the management in the lower left corner, select settings, and then search for "snippets" to see if the relevant options are turned off.
If those are opened normally, it may be that the relevant extension is missing, then you can click the extension on the left, and then search for the relevant language extensions.
got this really odd and frustrating issue on my android tablet/android phone, got a webapp (html5/javascript/css) that works fine on chrome desktop - but on mobile and tablet chrome, it happens all too often that when i click into a new page, then the output in the browser is just a pure black page.
What i then can do is to either rotate the device so the screen switches orientation and then the page appears like magic, or i can ex press the multi-tab button and then just click back and it shows.
So it somehow seems to be about redrawing not reloading the page.
Its not everytime it happens but it happens quite alot and i get nothing in debugging or any hints to what is going on.
Looked through the internet for similar issues and there are a few but they are either not replied or they are focused around some youtube issues back some time, or very old issues (2011/2012) - nothing that really points into the problem here.
Anyone have any idea here or input to how i can fix this without having the user to rotate the screen all the time ? its really affecting the usage.
note 1: it is quite heavy on some places on javascript so its not just a standard webpage
note :running latest android latest chrome on android
Look here. It's the same bug.:
How to fix black screen on Google Chrome mobile load page
The bug got fixed Feb 28: https://bugs.chromium.org/p/chromium/issues/detail?id=933374
But it doesn't seem to have made it in the next version of Chrome Android: https://chromium.googlesource.com/chromium/src/+log/72.0.3626.105..72.0.3626.121?pretty=fuller&n=10000
But the next version again should release with the bug fix (mid April?).
Meanwhile, did you find an easy js workaround for this issue?
Our site is currently useless until this bug-fix get released for Chrome Android?
On iPhone and iPad i have a wierd problem arround one website and Safari. Website is online shop and when someone order products and fill credit card info, on submit get auto-fill info about storing credit card info. Whether you click Yes or No, safari crash. I reviewed the CSS that transition property not made a problem or some jQuery code but I have not found a problem.
Site use Bootstrap v3.3.2, jQuery v1.11.2 and jQuery UI v1.11.4 in side design. Is not my design but I need to fix that mess now.
Maybe this is a webkit related bug? I was experiencing something like this a few weeks ago on OS X (Chrome dev build channel). There was an issue opened on this bug on the Chromium issue tracker.
I had a similar problem too, i was working on something that needed lot of listener.
In one point Firefox crashed but other browser were fine.
Just bind listener on what you need, dont forget to unbind everything else.
But without a link we can just make hypothesis
Here is one strange thing. Thanks for ideas.
My Chrome browser does not interact with some web pages as expected. When opening the pages on a different device (such as Browserstack or colleages' computers), everything works fine. There must be a problem with my device, it is obviously not linked to the browser version itself.
Example 1: click on element does not show reaction
When clicking on the small gray dots below the main image here, Chrome usually performs a caroussel switch. On my device, it does not. Clicks are constantly being ignored, although the automatic caroussel switch works just as on any other device.
Screenshot: i.stack.imgur.com/KR64m.png
Example 2: click on button does not show reaction
When clicking the button "Weiter" on this page in the lower right section of the page, my Chrome does not show any reaction. Works as expected on any other device.
Screenshot: i.stack.imgur.com/g8dHN.png
My Chrome Version: 33.0.1750.146 m (plugins disabled, surfing in anonymous mode)
OS: Win 7 Pro SP1 64 Bit
Thanks for help!
UPDATE:
I found out that my Chrome shows different results to a VisualEvent-check than Browserstack.
Have a look here:
My chrome (buggy): i.stack.imgur.com/Earrs.png
Browserstack (working): i.stack.imgur.com/zRRgA.png
What can I learn from that? There are two more event handlers
There are no VisualEvent differences for the second example, however.
UPDATE 2: On a MS Virtual Machine, everything works as expected:
My comment below
Hm do you deactivted your Javascript by accident?
https://support.google.com/adsense/answer/12654?hl=de
Have u tried a different browser on the same device?
I had this problem too, but it was solved by itself the next day. Maybe you just need to do a reboot?
Concerning my device, the issue is related to the fact that my device has a touch screen which Chromium does not know how to handle in the standard configuration. Considered a bug.
nzolghadr#chromium.org
The problem is with "'ontouchstart' in window" expression which the jquery.flexslider library uses. Right now on Windows Chrome returns that as true when you have chrome://flags/#touch-events enabled/automatic. Related issues are: crbug.com/467934, crbug.com/555746, and crbug.com/392584 which based on those it seems that Windows thinks something is touch enabled and Chrome just reflects that.
https://bugs.chromium.org/p/chromium/issues/detail?id=373991#c13
I have written a word game using HTML5 canvas tag and a little bit of audio. I developed the application on the chrome web browser on a linux system. Recently during the testing phase it was tried on safari 5.0.3 on Mac and the webpage froze. Not just the canvas element, but interactive element on the page froze. I have at some times experienced this problem on google chrome when I was developing but since the console did not throw any error before this happened, I did not give it much credence. Now as per requirements I am supposed to support both chrome and safari but this dismal performance on safari has left me shocked and I cannot see what error can be thrown which might lead to such a situation. Worse yet the CPU usage on using this application peaks to 70-80percent on my 2yr old macbook running ubuntu... I can only but pity the person who uses mac to operate this app, which undoubtedly is a heavier OS. Could someone help me out with a place I can start with to find out what exactly is causing this issue.
I have run profiles on this webapp on google chromes console and noticed that in the heap spanshot value increases steadily with the playing of the game, specifically (root) value which jumps up by 900 counts. Any help would be very appreciated!
Thanks
EDIT: I don't know if this helps, but I have noticed that even on refreshing the page after the app becomes unresponsive the page reloads and I am still not able to interact with the page elements but the tab scroll bar continues to work and I can see my application window completely. So to summaries the tab stops accepting any sort of user interaction inside the page.
Edit2: Nop. It doesn't work still... The app crashes on double click on the canvas element. The console is not throwing any errors either! =/ I have noticed this problem is isolated only to safari!
Edit3: Okay, so I performed some other tests today. I isolated the HTML5 widget and its HTML data only and ran it on safari locally to reproduce the error. Alas it works well! So I tried playing the game from my server without Facebook integration, and it works fine again! So The issue crops up only on safari on MAC OSX, while the widget is on Facebook canvas as a Facebook application. I am very hard-pressed to come up with a reduced test case scenario for this app... =/ It gets weirder, the game works well on safari for windows. Also after the tab freezes the other tabs continue to be responsive and well working. This tab too closes on clicking the close button and stuff, but if I load another page on this same tab after its frozen the page loads in the tab canvas, but I cannot interact with it. Not even google.com! So I am sure there is no bug with my game but its a safari bug... Will soon file a bug report, thanks for all the help people... :)
What you should do, in one sentence: Reproduce the problem with as little code as possible.
Start removing parts of your app until you find nothing that can be removed while still preserving the error. Start by throwing out external resources (css, images, etc) and leave just the html and javascript. Try removing the audio. Try removing as much gaming logic as possible. Try removing all user input code.
If this truly is a bug in Safari itself and not in your code, it should be possible to create a very small code example. Until you have that, saying "my web app doesn't work in safari", without any details or examples, will get you nowhere.