I activated devtools experiments in
about:flags
but nothing shows up in settings.
Has something changed or is the feature gone? thanks
Chrome DevTools used to have a canvas profiler, as Garbee mentions, but unfortunately it was removed. (There have also been other Chrome extensions for general canvas inspection, but AFAIK none of them are still working/maintained)
Firefox has a general canvas debugger that's quite good: https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-developer-tools/
Safari also added a canvas inspector that you can turn on.
Also note: there may be an extension for your framework (e.g. the three.js inspector).
The experiment was removed. As far as I know it was never made stable, so that functionality is gone completely.
Related
I created one simple nuxt project. Every time when I try to change something in chrome dev tools (for example check and uncheck some css), other css styles will be removed.
Does anybody know why this happens?
The problem happens only in chrome and opera. In Firefox it doesn't happen.
Safari's Web Inspector is absolutely awful, and it keeps crashing on me. One of my colleagues suggested using Chrome Devtools to inspect Safari pages via Remote Debugging. I haven't found anything on Google for how to do such a thing--is that possible?
Safari and Chrome use different debugging protocols (initially these were very similar, but over time they grew into separate things). Thankfully, there is a Google project that does the translation between these protocols - iOS WebKit Debug Proxy. It doesn't mention desktop Safari though.
I've been using Chrome forever for development, but it seems as if the last few versions - they've changed the functionally of the Web Inspector.
For instance, before I was able to search the 'Resources' tab, but now I have to search via the console, which makes it less easier than the way before I think Chrome 31.
Is there a way to rever back to the previous Web Inspector?
Same thing with Safari, but they changed their Web Inspector long before...
Thanks,
Roc.
Until recently, when paused in Chrome debugger on a breakpoint, the current state of a JavaScript variable, array or object would pop up in a yellow dialog if hovered over with a mouse. That is no longer working though I'm at a loss to know what has changed. Has anyone else experienced this? It's really making debugging a lot more difficult on this computer. My other computer still has the normal behavior in Chrome Dev Tools (both Windows 7 machines). Thanks in advance.
The same thing happened to me on 16/12/19, with version 79. But in Chrome canary, it is working fine. People who need can download it here (you can use it for now) or you can use Chrome Dev here
For the people who don't know about Chrome Canary or Dev
Chrome Canary is an experimental version of the popular Chrome browser. Google offers four release channels for its Chrome browser: Stable, Beta, Dev, and Canary. Most people use the Stable release of Chrome, which is rigorously tested and considered very reliable.
By contrast, Chrome Canary may appeal to people who like noodling around with new technology and want to get an advance look at what the standard Chrome browser may look like in the future.
Updated my chrome to version 79.0.3945.117 (Official Build) (64-bit). popup after hovering to variable is not showing.
Luckily, I found solution on google(don't know about the source now). Simply turn off the
Hardware acceleration feature and it worked. If you ignore impact of hardware acceleration turn off, this is the ideal one.
Canary version 81>= is another solution for this feature to work.
This was resolved in a later version of Chrome and is no longer an issue.
I am using GWT-JAVA. The Login page displayed good in firefox.
But In IE It is too slow and also Fonts are too big.
In chrome it display only the background image. Nothing will be display.
Is it GWT a browser dependent? Otherwise Can i change any other options or anything else?
Thanks in advance.
GWT is intended to be browser independent, but there are limits. Are you following the advice in the "Cross-Browser Support" page?
Speed of old versions of IE will always be an issue for any browser-based UI toolkit that relies heavily on Javascript.