I have been getting a problem where my drop down menu is not working. Whenever I try to open a drop down menu it closes it automatically within a second. It used to work fine and I have not downloaded anything that should affect it.
I have tried:
Re-installing Chrome
Checked for malware with Chrome and all other trusted anti malware software
Disabled all extensions and tried incognito mode
Installed Google Canary with same issue still appearing
Cleared history and cache.
Updated Chrome to the newest version
I have tried every single thing I could find as solution but with no success. It started a few months ago and I am not sure why.
The issue is Chrome only and does not happen in Firefox or Microsoft Edge.
This issue happens on every site with drop down menus.
If anyone knows the solution to this it would be amazing.
The issue is in PNG attached file
Huion tablet is the culprit in my case, the symptom is gone if I close the huion tablet app.
Related
After a recent update to Chrome dev (88.0.4315.5), all the possible columns in the network tab are shown and i cant hide any of them. I've tried right clicking the header and unchecking but nothing changes.
here's a screenshot of the problem
Also encountered this problem today, I'm using Chromium Nightly build.
Downgraded to stable, and everything fixed
I am creating a small project and for the front end I chose to use Material Design BootStrap (with jQuery), since I like those designs more than the standard BootStrap. Until now everything had worked correctly, but I noticed a strange behavior with one element: the drop-down lists. When you click on a list, it is displayed, but then there is no way to close it again, that is, to do the show / hide function when there is a selection, or when you click somewhere. It just stays open. The only way to close it is to refresh the page. This happens to me even on the MDBootstrap page. (https://mdbootstrap.com/docs/jquery/navigation/navbar/).
Well, some additional data: So far I had done my tests using the latest version of Chrome. I found it strange that such elementary functionality did not work even on the website of its creators. Then I tried Firefox, the same problem. Today in the morning while working, I decided to open the MDBootstrap page on my work computer, and to my surprise the drop-down lists worked correctly! I also did the test on a MacBook with Chrome, entering the same page and it also worked. I even tried from a virtual machine, and in the Chrome of this VM the drop-down lists worked!
In summary, MDBootstrap drop-down lists do not work, so far, in Chrome or Firefox on my personal computer at home. It occurred to me that it could be the extensions of those browsers that were causing some conflict with that element, but I uninstalled and reinstalled both browsers, and the problem persists. I have tried incognito mode with these browsers and it does not work. I tried Internet Explorer and Vivaldi, and in these if the drop-down lists work. Everything is so confusing!
Well, it's my first query on StackOverflow. If you can think of any other possible solution, or why this problem arises, the suggestions will be well received.
I am trying to execute chrome as
chrome.exe --overscroll-history-navigation=0 --disable-pinch
with the --disable-pinch --overscroll-history-navigation=0 flags in command line but it does not work at all.
I am using Chrome Versión 73.0.3683.75. It does not forbid the overscroll gestures.... I am about to go crazy....:|, it worked perfectly but stopped working at some point last week.
Any help is sooo welcome. Thanks!
I have also been battling this one but have finally found the solution that works for me. It seems that since a couple of chrome versions back the overscroll-history-navigation flag has been removed from the command line options. However, you can still access it from the chrome flags page by visiting this url in chrome:
chrome://flags/#overscroll-history-navigation
and manually disable it there.
Unfortunately this didn't solve it for me as I am also running the --kiosk mode switch for a touchscreen kiosk application developed in HTML and I cant expect every user to go to the flags page to disable this.
What did work was to add the css overscroll-behavior tag to both the html and body tags in the css for the application:
html,body {overscroll-behavior: none;}
Problem solved! No annoying swiping navigation on chrome. Not sure why if the --kiosk switch is enabled this sort of behaviour isn't automatically switched off?
Anyhow, hope this helps you too.
For some unknown to me reason, I cannot select sap.m.IconTabFilter, like it's not pressable (on mouse hover pointer is not appearing and when I press, nothing happens). This issue is experienced in Chrome. In Mozilla it works fine.
When I copied the XML into JSBin in Chrome, it worked fine.
Did anybody stuck with the same problem? How to fix it?
I tried to clear cache, restart browser/pc - the issue persists.
Also, same issue I'm experiencing right now with sap.m.Switch control.
UPDATE: I think it's a PC-specific issue. The problem is that in Chrome the app decides it's running on a tablet (instead of a laptop. The laptop can work as tablet too, but I run the app in laptop mode). This applies corresponding app's behavior. Maybe this can be the root of the problem?
No custom CSS is applied, only default ones.
I assume you are using Chrome 55+ which comes with active PointerEvent and won't work with certain UI5 versions. You need to upgrade to 1.28.42, 1.38.14 or 1.42.8 or deactivate the feature in Chrome via:
chrome://flags/#enable-pointer-events
in the address bar.
I'm using Chrome-compatible SRWare Iron 5.0.381 on XP, and was checking out what Chrome has to offer to developers, EG inspecting the contents of the DOM of a currently-loaded web page.
But when I hit CtrlShiftI, the bar is totally empty:
Does someone why this is? Do I need an add-on? Are there other Chrome-compatible tools I should know about?
It appears you’ve found a bug in that fork of Chromium. The inspector works just fine with Google.fr in the latest Google Chrome and Chromium builds. Why don’t you use one of these browsers.
Usually the reason of that is some problem in DevTools JS code.
It is a chance that problem will be solved by chrome restart.
Such kind of problems can happen when chrome is upgrading at background.
The other reason of that can be some changes which you made in DevTools.js.
Of cause if you have done some changes :)
You can troubleshoot such problem by another instance of DevTools.
As example you can try to load DevTools.html page into Safari, open WebInspector for it and check console messages.