Windows 11 (using vscode) javascript autocomplete don't work - javascript

Good evening, I come to you because recently my autocomplete on vscode (especially in javascript) does not work anymore, I have another PC with the same version of it so I made a copy of the files on my other PC but still nothing. I also tried to completely reinstall vscode but still nothing
Any idea ?

Hi!here is my suggestion.
You can enter the management in the lower left corner, select settings, and then search for "snippets" to see if the relevant options are turned off.
If those are opened normally, it may be that the relevant extension is missing, then you can click the extension on the left, and then search for the relevant language extensions.

Related

How can I achieve bookmarklet functionality in Microsoft Edge browser (without installing anything extra)?

Microsoft Edge browser does not support javascript bookmarklet in favorites.
Is there an easy workaround for this?
When browser extensions for Edge come out, then it might be possible if the user installs an extension -- but that's much higher overhead for the user and developer.
I assume this is by design. But what is the microsoft workaround for this besides extensions?
description of problem:
http://answers.microsoft.com/en-us/windows/forum/apps_windows_10-msedge/please-support-drag-and-drop-bookmarklet-and/dc7d2f09-8742-46a5-bb4a-4d1f576b8919
and old workaround: http://www.howtogeek.com/231775/how-to-install-and-use-bookmarklets-in-microsoft-edge/
a hack using an installed program:
http://www.emmet-gray.com/Articles/EdgeManage.html
After experimenting around, I found out that in fact EDGE does support bookmarklets, but they call it Reading list. It works almost like bookmarklets, but a bit more poorly and difficult to debug, plus there is a (logical) limitation that cannot be circumvented as easily as in say Firefox: if your script comes from a http:// site, it cannot be run on a https:// site.
You can use bookmarklets in Edge this way:
Right-click your button with your javascript:.... url.
Click Add to reading list.
Navigate to your site and run the script on that site by clicking Reading list (Reading list on my version of Edge on PC is located behind the three horizontal lines called Hub and then the fancy icon with many curled horizontal lines called Reading list, on mobile the Reading list icon appears above the address bar when you click the ... menu icon) and from that list clicking your script.
I have tested it AND IT WORKS ON BOTH PC EDGE AS WELL AS MOBILE EDGE (Mobile: Windows 10.0.14393). Hope this helps someone as I almost abandoned my Lumia for an Android mainly because of my perceived lack of this feature.
With Windows 10 Fall Creators Update, Edge now supports editing URLs for favorites.
Reference : https://blogs.windows.com/msedgedev/2017/10/17/edgehtml-16-fall-creators-update/
Edit URLs for favorites
By popular demand, we’ve added the ability to edit the address for
individual favorites in the Favorites Hub or on the Favorites bar.
To do this, simply right-click or press and hold a favorite and select
“Edit URL.”
Points to Note:
The javascript code that's pasted in place of the URL should be in a single line. [i.e. remove all the new line breaks.]
The javascript code should not exceed 2083 characters.
Now that Edge supports editing a URL on the favorite bar - simply do the following.
Add a favorite (doesn't matter what)
Use "Inspect element" from the bookmarklet button context menu (right-click)
Use "Edit URL" from the favorite (create in step 1) context menu (right-click)
Paste the bookmarklet URL
(tested on 41.16281.1000.0)
I know this is kinda an old question, but...
Now that Microsoft Edge stores its favorites in a database, the "old workaround" is no longer viable.
But, there is a free 3rd-party application called EdgeManage that will allow you to edit/create the URL directly in the favorite.
So, this will allow you to use bookmarklets in Edge
PS: I am the author
I'd be happy to discover a better work-around, but the closest I have found for MS Edge version 92.0.902.78 is a feature known as "Snippets". The devtools guide describes Snippets as alternatives to bookmarklets.
To add a "Snippet":
Open the dev tools (F12 or Ctrl-Shift-I or navigate: ...->"More Tools"->"Developer Tools")
Find the "Snippets" pane in the "Sources" panel
Click the "New snippet" button
Add your javascript code in the editor area and save
To run a "Snippet":
Right-click on the snippet name in the Snippets list of the developer tools and select "Run"
Each snippet is associated with a uri-looking link (like snippet:///add-library-proxy), but these don't appear to be recognized in bookmarks nor from in the address bar.

What is the current behavior of firefox for the ubuntu menu bar?

I'm trying to development an applet (https://github.com/lestcape/Global-AppMenu) to be used in the Cinnamon desktop. My intention is not modify or create any other code than not be cjs (javascript code). All that i do is:
Connect my applet to the com.canonical.AppMenu.Registrar and the Gtk
Dbus API.
Get all object path from the muffin windows manager (a fork of
mutter).
Read and ask things over Dbus and then show the result of
that. I used all patches of Unity desktop, as I'm a user of Ubuntu 14.04.
Nemo, Nautilus, File-Roller, gnome-terminal, VLC, SMPlayer, Evince, are examples of applications that currently are working. At the moment, I only have a problem with one application, and this application is Firefox.
I'm pretty sure that i do something wrong, just i don't have any idea of what could be.
Firefox called the com.canonical.AppMenu.Registrar service perfectly, i also can trigger the Alt key and firefox don't try to show the menubar inside the window, but after some time (a minute), he emit a layout change signal without menu items, and will show the menubar to the user inside the main window, as is "normally".
My idea is that: this could be, because i'm missing to call some aboutToShow, or because firefox require a confirmation that i receive the menubar, and he required really that this will be done for the same GDBus Connection where he exported the menu bar, but i can not be sure who internally will be handled in that way, as i'm on javascript.
Any way the firefox behavior, apparently is a behavior with an know cause, and what i try to find is the cause of that behavior, to then I will try to find a solution.
Thanks and regards.
Firefox and thunderbird require a returned confirmation value from the Dbus connection, as i say in the question. This value is not returned in the default cinnamon code, i force to return the value and now the problem is resolved. Thanks anyway.
Try to look at the about:config page and search for the "ui.use_unity_menubar" entry. As I know, this setting toggle between using unity global menu or normal menu. Maybe this could help you.
Good luck with your applet, I'm waiting for more stable release and then I will give it a try.

html5 drag and drop upload broken in chrome

I have been working on this bug for a while now , for some reason the drag and drop uploading I implemented on my site has not been working in chrome. No error messages or anything. Just when you try to drag a file over the designated area you get the mouse icon of the circle with the line through it. So after testing and testing and testing I came to realize that even if I go to the html5 Official demo page for the drag and drop it does not work there either in Google Chrome.
Has anyone ran into this? is there some type of security setting that got triggered in my Chrome browser that is preventing the drag-n-drop ?? I am concerned now that there may be other user that may run into this. Currently I check if the user's browser if HTML5 compatable and then only offer the drag-n-drop option, if not I fall back to the choose a file button. But now I'm learning that there may be a third case - which is mine now . I have the newest version of Chrome , but it just for some reason started blocking drag-n-drop a few days ago. It used to work just fine.
EDIT
the HTML5 drag-n-drop demo site
and I'm using Chrome Version 39.0.2171.65 m
I found strangely enough (on version 57.0.2987.110) that closing all instances of chrome, opening task manager and making sure it is fully closed, then restarting it seemed to get the dropping working again.
I'm not sure of a fix when this is occurring but I did see a bug report about this at https://productforums.google.com/forum/#!topic/gmail/RgPdExhVPMs but it looks to me like a browser update (as this was originally posted in 2015 and likely isn't a problem anymore) would fix it right up.

Let the user choose the keyword for my omnibox chrome extension

I just created a chrome extension using the omnibox api.
"omnibox": { "keyword" : "a" },
I found out that it is not possible to use multible keywords
or let the user choose a keyword for my extension although the extension is listed on the search engines settings page:
I addition to that the priority of the extension keyword is by far the lowest.
If a User already defined a keyword in the Default search engines / Other search engines - sections the extension keyword is not usable.
Does anyone know a solution for at least one of these issues?
Maybe by using the NPAPI?
This discussion has come up before and you can see an example of it here - https://code.google.com/p/chromium/issues/detail?id=75890.
It seems that the reason there is only one title:keyword pair is to prevent an over abundance of key words. There also does not appear to be any support that would allow for the end user to change this pair.
I'd like to let people know that it appears that this has changed and is no longer the case. I was exploring this possibility myself and found this page stating it wasn't possible. In order to change the keyword for my extension after installation I took the following steps:
Right click the omnibox (address bar) and select Edit Search Engines
Scroll to the very bottom (optionally deleting half of the really long list of sites you'll find)
Under the section for keywords for installed extensions, find the extension you wish to edit and click the keyword value to the right of it's name. There is no edit button, it will turn into an editable field.
I am using Chrome version 30.0.1588.0 on Windows, but I am not sure how long this has been editable.
For some extensions I have found it necessary to edit the extension source directly. Often this is available on GitHub or similar a repository.
Clone source to a directory on your computer
Open the manifest.json file in the extension's route directory. Edit or add this section:
"omnibox": {
"keyword" : "key"
}
Where "key" is the keyboard shortcut key itself.
In chrome, go to: chrome://extensions/
Delete the old extension (careful of deleting important data if relevant)
Switch on developer mode in top right of page
Select Load unpacked extension... and navigate to the cloned directory
Verify the extension has loaded in Chrome and works correctly
It is a security risk to browse the Internet with Chrome Extensions developer mode left on. Solve this by packing the extension into a single .crx file (a type of .zip file).
Delete the newly created "unpacked" extension and click Pack extension... (you can sign the file with a .pem key but this is not necessary).
Switch off developer mode in top right of page
Nagivate to the directory above the cloned directory
Drag the .crx file produced in the packing step onto the Chrome window
The new extension should now appear on the chrome://extensions/ page
Verify the correct result by navigating to chrome://settings/ -> Manage search engines...
At bottom of page under "Search engines added by extensions" the keyboard shortcut should be updated and extension only appears once

Get rid of [dynamic] JavaScript views in Visual Studio

Since I installed Visual Studio 2010 from scratch about 2 months ago, it behaves slightly different when debugging JavaScript code being run in IE.
When I set a breakpoint, it opens a duplicate of the view with the term "[dynamic]" in the header and marks the breakpoint in there.
When a JavaScript error happens during execution, it does the same before it marks the line of code that threw the error.
This "dynamic" view is editable but edits have no effect - they are not saved to the file.
I find this behavior pretty uncomfortable. Everytime I notice an error in the code during debugging, I happen to fix it in the dynamic view. I hit save. VS does not complain. Next I refresh the page in IE, and - bang - the changes are lost, it loads the untouched old version again.
I haven't been able to find out how I can turn these views off. Before I re-installed Visual Studio it did not do that. It would only create "dynamic" views for script found in inline script tags in HTML files.
Try this
IE > Internet Options > Settings (under browsing history) > Check for new version of stored pages : Every time I visit the webpage.
This works for me in IE10.
Other option is to open Developer tools and select cache option Always Refresh from Server as show in the image below
Try hitting CTRL+F5 on the web page. That did the trick for me.
The problem was that I had opened other IE windows from a previous debugging session, so the dynamic javascript files were still cached.
Having developer tools open - F12 - should also cause the cache files for the page to be cleared on each refresh.
Changing the encoding of the JS file in question, from a Windows codepage to UTF-8, fixes this for me.
Narrowing it down, it appears that OEM Extended ASCII characters in the file (e.g. ALT-254 which I use for a bullet) trigger the problem with the Windows codepage files.
(Visual Studio 2013 Update 5, IE11)
For Google Chrome:
Open developer tools(F12)
Open Network Conditions Tool
Select Disable Cache
I had the same problem of not being able to hit a break point in new code. And breakpoints on old code in the same page will bring up the [dynamic] version. The edited page is not reloaded. This just started for me a week ago in both VS2012 and VS2013. Using refresh page and/or Ctl-F5 did not work for me. BUT, reading this thread pointed me to using F12 to open Developer tools. Leaving that window open, while hitting refresh does the trick. Thanks guys.
1) Run the page Without Debugging (Debug-->Start Without Debugging)
2) While the web page is open in Internet Explorer, press Ctrl-F5 so
that the IE cache is cleared. Ensure IE has the focus.
3) Close IE and re-run the page with Debugging (Debug-->Start
Debugging).
This fixed the issue for me.

Categories

Resources