- 18 1月, 2018 9 次提交
-
-
由 Johannes Rieken 提交于
Add time variables for snippets
-
由 Daniel Imms 提交于
-
由 Daniel Imms 提交于
-
由 Daniel Imms 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Sandeep Somavarapu 提交于
-
- 17 1月, 2018 31 次提交
-
-
由 isidor 提交于
-
由 isidor 提交于
fixes #41734
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 isidor 提交于
-
由 isidor 提交于
fixes #41559
-
由 Benjamin Pasero 提交于
-
由 isidor 提交于
fixes #41663
-
由 Sandeep Somavarapu 提交于
Add copy command action to keybinding editor context menu
-
由 isidor 提交于
-
由 isidor 提交于
-
由 isidor 提交于
fixes #41706
-
由 Benjamin Pasero 提交于
-
由 Alex 提交于
-
由 Johannes Rieken 提交于
-
由 Daniel Ye 提交于
-
由 Rob Lourens 提交于
-
由 Matt Bierner 提交于
* Allow loading webview outside of file: origin **Problem** Webviews are currently always loaded from a file on the disk. This results in the webview running in the file origin, potentially allowing it to access any file on disk. If a webview fails to sanitize workspace or remote input, untrusted code could potentially access files on the user's system. **Fix** Add a new option to serve the webview out of a "data:" uri instead. This prevents access to `file://` resources. In order to allow webviews to still load resources from disk, add a new protocol called `vscode-core-resource://` that only allows access to resources inside of the vscode directory. Moves extension pages and our release notes to use this new option. These already are pretty locked down. We cannot move the htmlpreview command to use this option as it would break a huge number of existing extensions, however the new webview API will always have this new option enabled. * Shorted protocol name
-
由 Johannes Rieken 提交于
-
由 Rob Lourens 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Sandeep Somavarapu 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-