cbda1fdeb7
* Fix drag and dropping of editors for webviews Fixes #25854 This change does the following: - Have the webview editor create an `EditorDropTarget`. This is required because the webview itself is not part of the normal editor dom (it exists as a top level node in the workbench so that we never reparent it). This means that the standard `EditorDropTarget` does not work. - Make webviews set `pointer-events: none` while a drag is happening. When a drag happens on Electron's webviews or a normal iframe, no drag and drop events seem to get generated. The fix is to set `pointer-events: none` while the drag is happening. But it's also difficult to detect when the drag is happening because the `EditorDropTargets` class eats the drop event itself. The only reliable seeming way I could find to determine when a drag starts and ends is looking at global events on the window. This workaround is pretty ugly. I'm not sure if there's some better approach that would work with webviews * Add public `createDropTargets` helper on editorPart Unfortunatly we can't add this method to IEditorGroupsService as it uses the `HTMLElement` type * Rename function to createEditorDropTarget * Use instanceof instead of cast |
||
---|---|---|
.github | ||
.vscode | ||
build | ||
extensions | ||
remote | ||
resources | ||
scripts | ||
src | ||
test | ||
.editorconfig | ||
.eslintrc.json | ||
.gitattributes | ||
.gitignore | ||
.mention-bot | ||
.nvmrc | ||
.prettierrc.json | ||
.yarnrc | ||
azure-pipelines.yml | ||
cglicenses.json | ||
cgmanifest.json | ||
CONTRIBUTING.md | ||
gulpfile.js | ||
LICENSE.txt | ||
package.json | ||
product.json | ||
README.md | ||
ThirdPartyNotices.txt | ||
tsfmt.json | ||
tslint.json | ||
yarn.lock |
Visual Studio Code - Open Source ("Code - OSS")
The Repository
This repository ("Code - OSS
") is where we (Microsoft) develop the Visual Studio Code product. Not only do we work on code and issues here, we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.
Visual Studio Code
Visual Studio Code is a distribution of the Code - OSS
repository with Microsoft specific customizations released under a traditional Microsoft product license.
Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on Visual Studio Code's website. To get the latest releases every day, install the Insiders build.
Contributing
There are many ways in which you can participate in the project, for example:
- Submit bugs and feature requests, and help us verify as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to new content
If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Up vote popular feature requests
- File an issue
- Follow @code and let us know what you think!
Related Projects
Many of the core components and extensions to Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter have their own repositories. For a complete list, please visit the Related Projects page on our wiki.
Bundled Extensions
Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (code completion, Go to Definition) for a language have the suffix language-features
. For example, the json
extension provides coloring for JSON
and the json-language-features
provides rich language support for JSON
.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.