- 03 7月, 2019 2 次提交
-
-
由 Matt Bierner 提交于
#76442
-
由 Logan Ramos 提交于
-
- 27 6月, 2019 1 次提交
-
-
由 Logan Ramos 提交于
* Allow the error to be surfaced to the user to provide more information about what is happening * Testing gulp src * Move json to app root * Telemetry tooling commit update * Harcode telemetry commit * Update distro to match master * statSync try catch * build
💄 * fix build * make build fail * fix build * fix build * whitespace
-
- 25 6月, 2019 2 次提交
-
-
由 Logan Ramos 提交于
* Added telemetry command * Initial Build support * Added build logic for telemetry * Linux Builds * Windows builds sort of work * Remove arm telemetry extraction * Remove alpine telemetry extraction * Remove accidental s * More try catch
-
由 Benjamin Pasero 提交于
-
- 24 6月, 2019 2 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 23 6月, 2019 1 次提交
-
-
由 Sandeep Somavarapu 提交于
-
- 21 6月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
Fixes #75748
-
- 19 6月, 2019 4 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Matt Bierner 提交于
Fixes #72155 Adds a constant to the api that tracks the root path for resources inside of webviews. This is required because we will not be able to use `vscode-resource:` uris on the web. Our current approach is to rewrite the html we are given but there are almost certainly going to be cases where we don't get this quite right. Adopts the new api for the markdown preview
-
由 Peng Lyu 提交于
-
- 16 6月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
## Problem We use a custom `vscode-resource` protocol to control access to local resources inside of webviews. This will not work on the web, but we still would prefer a way to intercept webview requests from the main client ## Proposed solution Move webviews into their own origin and register a service worker on this origin. This service worker can talk with the outer iframe of our webview. When a request for a resource comes in to the service worker: * In the service worker, add the request to a map and post a message back to the client saying we want to load this resource * The outer iframe gets the message from the sercice worker and forwards it to our main process * This process handles the message and use the normal file system api to read the resource (also restricting which files can be read) * We post the result back into the inner iframe which fowards it back to the service worker * The service worker now resolves the pending request. The prototype version in this change works but does not correctly handle multiple clients existing at the same time (plus probably a lot of other edge cases too)
-
- 11 6月, 2019 3 次提交
-
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 08 6月, 2019 1 次提交
-
-
由 Sandeep Somavarapu 提交于
-
- 06 6月, 2019 1 次提交
-
-
由 Rob Lourens 提交于
for microsoft/vscode-remote-release#544
-
- 05 6月, 2019 1 次提交
-
-
- 03 6月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 28 5月, 2019 1 次提交
-
-
由 Joao Moreno 提交于
-
- 25 5月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 09 5月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 25 4月, 2019 1 次提交
-
-
由 Sandeep Somavarapu 提交于
-
- 15 4月, 2019 1 次提交
-
-
由 Martin Aeschlimann 提交于
-
- 12 4月, 2019 1 次提交
-
-
由 Martin Aeschlimann 提交于
-
- 11 4月, 2019 2 次提交
-
-
由 Martin Aeschlimann 提交于
-
由 Sandeep Somavarapu 提交于
- Scope machine settings - Make remote settings scoped to machine settings
-
- 10 4月, 2019 1 次提交
-
-
由 Andre Weinand 提交于
-
- 09 4月, 2019 1 次提交
-
-
由 Martin Aeschlimann 提交于
-
- 04 4月, 2019 3 次提交
-
-
由 Andre Weinand 提交于
-
由 Andre Weinand 提交于
-
由 Benjamin Pasero 提交于
-
- 03 4月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 02 4月, 2019 1 次提交
-
-
由 Jon Bockhorst 提交于
-
- 22 3月, 2019 2 次提交
-
-
由 Martin Aeschlimann 提交于
-
由 Matt Bierner 提交于
-
- 11 3月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 02 3月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-