This question already has answers here:
Some Emmet abbreviations in VSC not working, like '!' or using '*'
(8 answers)
Closed 7 months ago.
I have started to use Visual Studio Code and am having issue's with Emmet.
When I type in the code ul>li and hit tab to expand, it expands. But when I try to multiply the code like ul>li*3, it does not expand and I get no suggestion for that abbreviation. I have added "emmet.triggerExpansionOnTab": true to the json file, and that did nothing, and I have restarted all extensions with the restart extension host command.
All suggestions on how to fix this issue are appreciated.
Yes, I am facing this issue too since latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
After checking the box You can see the suggestion and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.
You can get them back consistently by turning Inline Suggest on.
If you find that annoying or distracting, you can leave that off and use ctrl+space to get the old popup shortcut to come up, and then hit tab as normal.
Related
This question already has answers here:
How do you inspect the web inspector in Chrome?
(4 answers)
Closed last year.
I have a Chrome extension, that runs (and displays) inside the Chrome dev-tools. (known as Extending DevTools)
I upgraded to version 97.0 of Chrome and since then, whenever I try to right click the mouse from inside the extension, nothing happens.
I need the right click in order to inspect my extension.
Any help will be much appreciated.
Edit:
This question is not a duplicate of other suggested questions. Although the accepted solution to this problem is the same as other suggested question, the cause of this problem is different. The problem of my question is that since version 97 of chrome, right click is disabled in some devtools-extensions. As pointed out by #wOxxOm, this problem is caused by this bug, whereas in other questions the poster directly wanted to know "how to inspect the devtools".
Thanks to #idoco for helping.
A nice workaround is to:
Open dev tools
Undock into separate window
Press option+cmd+i on the mac keyboard.
An explanation to why this issue happens can be found here:
https://microsoftedge.github.io/edgevr/posts/attacking-the-devtools/
I'm just trying vscode one more time after a year or so. I'm using it for web development so really want the html snippets to be working, but none of it is, I don't get any suggestions, and typing ctrl-space brings up a box telling me there are no suggestions. What do I need to do to get this to work. It's a completely fresh install on a freshly installed Linux Mint20. I always thought this part worked out of the box, it did 2 or three years ago when it was using it on a mac, I expected a similar behaviour to be honest. do I have to enable another setting to allow intellisense to work. I've no idea, it works out of the box on a mac.
So I found the solution after 5 hours, it's at the bottom right of the screen, file type should be "HTML" or whatever file it should be, not just "plain text". Vscode will pick this up from the file extension, but for testing, I just clicked file - new file, which of course will be plain text by default.
Feel like a bit of an idiot, but hopefully this will save someone else trying to fix this.
I've added a DOM breakpoint for "subtree modification" to the body element.
When I remove the DOM Breakpoint via "Remove breakpoint" or "Remove all DOM breakpoints" and reload the page the DOM breakpoint is there again.
Is there another way to remove the DOM breakpoints?
Just for the record: This happens only for "subtree modifications" breakpoints. "node removal" or "attribute modifications" work.
One of our devs in the company had this same issue, We fixed it by going into chrome dev tools settings and restoring defaults.
Open Chrome dev tools, Press F1 the then just Restore Defaults. That seems to have fixed the issue for my colleague.
The F1 works on mac at least, If it docent work for you use the three dots menu in the upper right corner then settings.
I had the same problem plaguing me for weeks. None of the answers on SO are correct (the answers from 7 years ago are all invalid now since WebInspector doesn't exist).
The only way I was able to fix this was to uninstall and reinstall Chrome. I know, this solution sucks but Google closed the bug 7 years ago and refuse to re-open it. Yay Google.
Anyway, I can confirm reinstalling fixes it for me.
This question already has answers here:
How to check for duplicate CSS rules? [duplicate]
(3 answers)
Closed 6 years ago.
I've been using the "Emmet Livestyle" plugin lately, and its been flawless. But on the last commit to my github project I noticed that the css lines were duplicated* from 1446 to 3448. I then opened chrome dev tools and confirmed that there were like 3 same styles per one element. I suspect that plugin is the culprit to this problem.
I really need to remove the duplicates. But I don't know where they start or where they end as the file is pretty large.
Could you guys happen to know any online tool or sublime plugin that could help me with this ?
Thanks.
I've had this exact same problem with LiveStyle with my files being duplicate somewhere around 4 different times. One file is now 4 times as long.
In searching for a solution I found a NodeJS plugin called css-purge. It IS the solution and as far as I know, the only solution. I guarantee it.
You can find it here CSS Purge Package Install Page. Be sure to install NodeJS properly on your system first. I'm on a Mac so these were my instructions. I'm still looking for a solution for fixing Live Style. It used to work flawlessly until this new dedicated app started causing problems.
If you look at Chrome's Developer Tools (other browser's do this as well), you will be able to, not only see what styles are being applied to an element, but from where those styles are coming from:
Once, you know the source, a simple "Find" operation in your editor will track the rule down.
The console gets stuck in a state where every two page refreshes a new closed instance of my indexedDB is displayed. They are all closed except for the one on the top and everything within the application still seems to function normally, however other strange things occur when using the console.
When I click on a table within the database it shows the data, but when I try to filter or go to the next page it all disappears. I have to completely close the browser tab and then reload.
Sometimes when I enter in console commands they don't do anything, don't return anything (not even undefined), but when I refresh the page it alternative between working and not working.
Let me know if you need some more information. I haven't a clue what's causing this. I'm using the latest version of Chrome 35. Any thoughts?
Saw this once. Try a fresh install, and if that does not work, try upgrading to dev channel 37. I did both those things (for other reasons), but have not been able to reproduce the bug since. Trudging through Chromium's list of open issues or changes might also help.
Also, it looks like your question is not really about programming so it might be closed. There are other 'something.overflow' sites to post this type question.
Edit: also, regarding the disappearing issue, I actually reported this bug on Chromium. It was recently fixed!