I've been looking for an answer for a while now and I can't seem to find any reasons why this is an issue. I have various places in my style sheets where I use cursor: pointer for UI elements like buttons and links. The majority of the time it works as I expect, but occasionally they just don't want to work. I'd love to say I have a specific example in the style sheets that would ensure replication but that's been the issue. When it happens, it's not just for one element, it's for all of them. I've experienced this across the board with modern browsers and it seems to just be completely random which makes it hard to troubleshoot.
The only thing I've been able to confirm 100% is that if it does happen, I can open developer tools, then select an element to inspect that is supposed to have the cursor: pointer and the effect begins working everywhere again. I'm not sure what's going on here and it's driving me up the wall.
Is there any documentation surrounding this issue or something similar?
I experience it in localhost.
I haven't noticed it in production.
I haven't noticed it on JS Fiddle or Codepen when creating wireframes.
Is it a localhost issue? I've even thought it may be related to something I had done prior, but it happens even as I just navigate the site while debugging, sometimes it works on one page, but come back to the same page later in the session and it may not work anymore.
I know this one's tough and there's not a lot to go on. I don't usually make posts without code, but I'm just wondering if anyone else has experienced the same or a similar issue and resolved it.
I too have experienced this. It's actually not a code issue at all. I've found that the cursor: pointer bug you're experiencing is directly related to the Visual Studio 2017 (and newer) remote debugging browser window.
Solution
In Visual Studio, disable "Enable JavaScript Debugging for ASP.NET (Chrome & IE)".
At the top of your Visual Studio window, go to Debug -> Options. The highlighted item in the screenshow below must be unchecked:
This was a feature added in 2017, and while it helps with debugging JavaScript and TypeScript, it does so by launching a plain browser window ("remote debugger"); that is, no extensions, no bookmarks, no history, etc. The remote debugging browser window seems to have its fair share of bugs.
I saw this same behavior but not while debugging through visual studio. If I hit F12 to go to the Chrome dev tools, then click on an html element. The cursor goes to the style listed according to the style sheet.
Related
I noticed recently that when using Chrome or Safari for developing, I see this little indicator in the upper-left of the screen that shows me the load time of the page. If I click on it will change positions I think, and disclose a larger panel showing more info about the page load.
I feel a little silly but I don't know what this is -- it isn't an extension AFAIK (I disabled all extension), it happens in BOTH Safari and Chrome, and it only happens when developing on 127.0.0.1 or localhost
SO.. my question is, can I 1) disable it, or 2) move it to another corner on the window?
It's a patently straightforward usecase: All I want to do is take a screenshot of the "Hello World" that is below the indicator, but it is covered up.
I don't remember seeing this until recently I am assuming it is something I just never noticed or something new in Webkit
UPDATE 2021-03-13
Does it let you inspect it in developer tools, perhaps by using mouseover selection? Its attributes and CSS classes might give you something specific to search for.
Yes I can inspect it. it seems to be on my page. I wonder is this from Ruby on Rails? huh?
it looks like so:
Does it happen in Firefox? If so, it's probably not a browser thing, but a server thing.
Yes! Another good call my friend. So, not webkit or browser you're right.
What http server are you using? Could it be adding the thing automatically?
It must be something new in Ruby on Rails that I never noticed before. I will confirm and post here again.
What you're looking at is called https://github.com/MiniProfiler/rack-mini-profiler and can be enabled and disabled at will using Alt+P.
You can verify this by clicking an entry and clicking more. At least on the version I am using, it will report that you are looking at rack-mini-profiler, like so:
This has to be a programming question, relevant for stack-overflow, but there might be something I'm missing.
So, has anybody else observed this problem?
(This would be easily recreatable only to people who use multiple languages regularly.)
My problem is this: to swap between my two languages, I normally use the alt+shift shortcut. This works everywhere, for example it works in MS office, chrome and firefox, notepad, visual studio... it even works on the Microsoft Edge's search bar. However, when I am typing in an html element in Microsoft Edge in Windows 10, it doesn't.
Until now I have to either change the language from the taskbar, using the mouse (which is slow), or take the focus off the control, use the shortcut, and give the focus back to the control (which is slow but also annoying)
Anybody know to help me with this?
I'm interested in understanding what's wrong more than solving it, since I can always use another browser.
PS: If I was as frustrated as I am now, I would whine about how Microsoft manages to keep making things that everybody else has solved ages ago, difficult.
I realize this is a very general question but we are wondering if anyone has any suggestions in trying to troubleshoot why Chrome hangs sometimes when rendering certain pages on our site. It's intermittent. We've tried checking out all the plug-ins, disabling, etc. Just can't come to any rhyme or reason why it's happening. Any pointers on how to troubleshoot and resolve would be appreciated. It's an ASP.NET MVC site. Internet Explorer has no issue. Thanks.
Without more details it isn't going to be possible for someone to answer your problem for you, but if you can invest a two or three hours in the problem then you may well be able to solve it yourself.
As the issue appears in Chrome then you may be interested in the free "Discover DevTools" course run by Codeschool and sponsored by Google (you have to register in order to follow the course, but it is free).
I suspect that the issue will turn out to be related to a memory leak where large numbers of elements are being added to and removed from the DOM using JavaScript, or the same element(s) are being added and removed multiple times. The course specifically covers "Memory Profiling" using Chrome Dev Tools, as well as the specific problem of memory leaks - the cause of them and how to resolve them.
If it is a memory leak, then the issue will closely correlate with the amount of time the page is open within the browser, especially if it is a result of one or more elements being frequently added and removed as a result of user interaction.
I've been doing a lot of testing in IE10 lately, and have recently ran into a very strange error.
Right after closing a jQuery UI dialog, IE10 opens up a cursor and allows the user type directly into the page. However, there are no inputs for them to be allowed to put things in, and from using Microsoft's F12 Developer tools, it seems that it is writing directly into the DOM -- an area that was a 'Text - Empty Text Node'. I have no idea where these nodes are coming from, or why the user can put text into one of them. I really have no code to show because it seems to be tied to nothing, and as I keep cutting away layers it still seems to be there.
Has anyone else ran into this? It seems to happen in IE9 as well. I'm at a loss here.
EDIT: In addition, I thought it may be helpful to say that I'm using jQuery datatables here.
Okay, so I have made some progress on this.
It turns out IE10 isn't writing data directly into the DOM -- instead, it dynamically created a text input, didn't recognize it, and then deletes it. You can type directly into it, but if you click off or focus on anything else, then it disappears and leaves completely.
I've still not diagnosed the source of the issue -- I know it only happens in IE, and may include datatables or jQuery UI. I tend to believe it's IE specific, because it's such a rare action and there's no trace of it anywhere else.
Hope this dialog helps someone else down the line. If you find a better answer, please post it!
I use Chrome's Developer Tools a lot and on the whole I prefer it to Firebug, but one thing that I've been noticing lately is that sometimes it fails to show my pseudoelements in the styles area. Sometimes it does, so I know it works occasionally, but some, seemingly, random times it doesn't. The obvious response to that would be "are you sure they are set up properly?" Which I consider each and every time it happens. But the elements are visible in the template, they just don't show up in the styles so I can't edit them.
I'm referring to :before and :after mainly because thats what I use the most.
Has anyone else had this problem? If you haven't, I'm sure this will be hard to answer, but I'll supply any more information I can. I would show you the example where I'm having trouble but it's on a private server.