I noticed the strangest behavior on my Mac (macOS Big Sur 11.6, Apple M1) in any browser (Firefox 96.0, Chrome 97.0.4692.71).
When my cursor hovers over a link, it turns into a hand for an instant and goes back to an arrow straight away. It's like it wants to show the correct cursor, and then overwrites it.
Even having an !important to the CSS property of a link doesn't change this behavior.
Does anyone have an idea how to change this?
A video of the behavior, W3C page is used via WeTransfer:
https://wetransfer.com/downloads/37b8e4a034cbeee674fb480bf055144f20220114093334/77efdb
On an other computer (macOS Big Sur 11.2, Intel Core) I don't have this weird behavior.
I can't find anything decent online about this, my apologies if it's already mentioned somewhere.
After a few hours the behavior was gone.
An entire reboot would probably have solved it too (I only shut down the browsers and even upgraded them, but even that didn't change the behavior).
As Jaime S mentioned, this issue also mentions it CSS cursor pointer flicker once and then back to default
Related
I am trying to troubleshoot some error that is causing any window on any app to quickly get grayed out for a dussin milliseconds, and at times get grayed out without getting "clicked back" again. I don't know if the issue lies in the cursor since it happens regardless of the current cursor location. It happens at least five times a day, and every time it happens it is very distracting.
I thought this could be caused by the trackpad clicking it out by itself since I've had issues with the trackpad a while back. But that doesn't make any sense since the location of the cursor is unaffected.
I have tried chrome, and other mac apps, but the error has persisted.
I have also tried full-screen mode on youtube (not browser full screen) but the same thing there.
I don't know if this could be relevant, but I have coded python a tiny bit although not more than installing a few packages. Though I coded python after this error started.
I want whatever error that causes app windows to get "grayed out" to be fixed.
Macos 10.15.5 Catalina
I cannot work any more with Intellij Idea, under OSX. After performing an IDE upgrade, the IDE main window (and any dialogs) has stopped responding to mouse clicks. The menu still works.
I have tried setting the log level to trace, with no success in getting any information of a possible exception when reacting to a mouse click.
The system is generating some thread dumps (a lot more under 2016.2, I have now downgraded to 2016.1.4). Is there a way to get more information to diagnose this issue?
I had a similar issue. It turned out it was my mouse (Microsoft Sculpt wireless) that was causing the issue. After plugging it out and using the touchpad, it suddenly started working. The issue is not 100% reproducible, though. It sometimes works fine, sometimes doesn't
Upgrading OS X helped once, but then the problem came back. Updating IntelliJ and even reinstalling it with removing all data never helped.
#edit: I borrowed an identical Microsoft Sculpt Desktop set from my friend - it worked fine. I bought another one for myself, and so far it works (it's been 3 months now). Weird indeed.
I have a strange issue whit my emulate touch functionality on Google Chrome version 49.0.2623.110 m.
I'm using laptop + monitor (both Dell) and running Windows 8.
The issue is that while Chrome is on my secondary monitor and touch screen emulation is enabled I cannot see a touch screen pointer (black circle) nor any kind of pointer, but when I move my Chrome to my main laptop display it would show. I tried disabling laptop display while using external monitor and it is the same, I cannot see the pointer. This was not a problem with previous Chrome version.
Did anyone had similar issues with this version?
Thank you
EDIT:
I've change the laptop, updated to win10 and updated Chrome to 50.0.2661.87 m version and I still have the same issue (colleague of mine has the same problem as well).
A colleague of mine "solved" the problem by enabling Windows' Mouse pointer trails at minimum length. I find it too annoying to work with the setting enable, but it does work if you really need it.
Mouse settings
They did some changes in recent version of Dev Tools and some options are now gone. Ensure you have "Mobile" or "Desktop with touch" selected, as you can see on the screenshot.
Generally speaking my font works fine but I'm seeing on odd occasions such as switching back to the browser from another application and sometimes when switching back from another tabs that my font seems to have unloaded and is using the fallback font.
I'm struggling to consistently replicate this and when I have seen it there are no errors.
I have also seen this happen in Chrome and Firefox on windows and osx and at a bit of a loss as to how this can be happening.
I haven't seen this issue in Firefox personally, but it is a known bug in Chrome.
https://code.google.com/p/chromium/issues/detail?id=336170
For some reason I am not aware of, one day the scrollbars in my App's DIVs disappeared.
I decided to finally look into the issue, but it's been days and had no luck.
Basically, you can scroll through these divs, however, the OS X scrollbars won't show up. If anyone could take a look and see what I am missing, I'd really appreciate it!
To replicate this:
Go to http://objectsapp.com/ with Safari or Chrome.
Use the search bar to search for: Inception
Position your pointer on the movie poster.
Scroll! (It will work, but scrollbars won't show).
Any idea why the scrollbars might be missing? (must be tested on OS X only).
Thank you!
You don't mention which version of Safari on OS X you're testing with so its difficult to determine what problem you're seeing.
In Safari 6.0 there was a WebKit bug that would cause elements with "overflow: scroll" set to not display the new overlay style of scrollbars. This issue was resolved in Safari 6.0.1. If you're using a newer version of Safari than that yet are still experiencing the issue, it's possible that you're seeing a different WebKit bug. If so, you could test the latest WebKit nightly build to see if the problem has already been addressed. It you still see it with the WebKit nightly build, I'd recommend filing a bug report.