Merge branch 'nw27' into nw28

rogerwang · rogerwang · commit c771c6680e38 · 2018-01-20T15:26:02.000+08:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,4 +1,11 @@
-0.27.4 / 01-05-2017
+0.27.5 / 01-15-2018
+===================
+- Fix: regression: webview devtools can no longer be embedded [(#6374)](https://github.com/nwjs/nw.js/issues/6374)
+- Fix: regression: devtools extension in embedded webview [(#6004)](https://github.com/nwjs/nw.js/issues/6004)
+- Fix: crash in node::PromiseHook when using Promise and johnny-five [(#6379)](https://github.com/nwjs/nw.js/issues/6379)
+- Fix: nwjs crash when choosing inspect when devtools are embedded [(#6375)](https://github.com/nwjs/nw.js/issues/6375)
+
+0.27.4 / 01-05-2018
 ===================
 - Update Chromium to [63.0.3239.132](https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop.html)
 - Fix: Kiosk Mode does not lock app in macOS 10.12+ [(#6169)](https://github.com/nwjs/nw.js/issues/6169)
diff --git a/README.md b/README.md
@@ -26,11 +26,11 @@ It was created in the Intel Open Source Technology Center.
 * Available on Linux, Mac OS X and Windows.
 
 ## Downloads
-* **v0.27.4:** (Jan 8, 2018, based off of Node.js v9.3.0, Chromium 63.0.3239.132): [release notes](https://nwjs.io/blog/v0.27.4/)  
+* **v0.27.5:** (Jan 15, 2018, based off of Node.js v9.3.0, Chromium 63.0.3239.132): [release notes](https://nwjs.io/blog/v0.27.5/)  
  **NOTE** You might want the **SDK build**. Please read the release notes.
- * Linux: [32bit](https://dl.nwjs.io/v0.27.4/nwjs-v0.27.4-linux-ia32.tar.gz) / [64bit](https://dl.nwjs.io/v0.27.4/nwjs-v0.27.4-linux-x64.tar.gz)
- * Windows: [32bit](https://dl.nwjs.io/v0.27.4/nwjs-v0.27.4-win-ia32.zip) / [64bit](https://dl.nwjs.io/v0.27.4/nwjs-v0.27.4-win-x64.zip)
- * Mac 10.9+: [64bit](https://dl.nwjs.io/v0.27.4/nwjs-v0.27.4-osx-x64.zip)
+ * Linux: [32bit](https://dl.nwjs.io/v0.27.5/nwjs-v0.27.5-linux-ia32.tar.gz) / [64bit](https://dl.nwjs.io/v0.27.5/nwjs-v0.27.5-linux-x64.tar.gz)
+ * Windows: [32bit](https://dl.nwjs.io/v0.27.5/nwjs-v0.27.5-win-ia32.zip) / [64bit](https://dl.nwjs.io/v0.27.5/nwjs-v0.27.5-win-x64.zip)
+ * Mac 10.9+: [64bit](https://dl.nwjs.io/v0.27.5/nwjs-v0.27.5-osx-x64.zip)
  * Use [Legacy build](http://nwjs.io/downloads/) for Win XP and early OSX.
 
 * **latest nightly build from git tip**: https://dl.nwjs.io/live-build/
diff --git a/docs/For Users/Advanced/JavaScript Contexts in NW.js.md b/docs/For Users/Advanced/JavaScript Contexts in NW.js.md
@@ -46,7 +46,7 @@ Different windows and frames have different contexts. So when you create a new f
 
 Some objects of Node context are copied to Browser context so that scripts running in Browser context can access Node.js objects:
 
-* `nw` -- the object of all [NW.js APIs](../../References)
+* `nw` -- the object of all NW.js APIs in **`References`** section
 * `global` -- the global object of Node Context; same as `nw.global`
 * `require` -- the `require()` function for loading Node.js modules; similar to `nw.require()`, but it also supports `require('nw.gui')` to load NW.js API module.
 * `process` -- the [process module](https://nodejs.org/api/globals.html#globals_process) of Node.js; same as `nw.process`
@@ -74,7 +74,7 @@ Scripts running in the Node context can use [JS builtin objects]() like browse
 **All node modules shares a same Node context in separate context mode**. But you have several ways to create new Node contexts:
 
 * Set `new_instance` option to `true` when creating window with [`Window.open()`](../../References/Window.md#windowopenurl-options-callback)
-* Start NW.js with `--mixed-context` CLI option to turn NW.js into [Mixed Context mode](#mixed-context)
+* Start NW.js with `--mixed-context` CLI option to turn NW.js into [Mixed Context mode](#mixed-context-mode)
 
 #### Access Browser and NW.js API in Node Context
 
@@ -96,7 +96,7 @@ In the browser side (index.html):
 <script>
 var myscript = require('./myscript');
 // pass the `el` element to the Node function
-myscript.setText(document.getElementbyId('el'));
+myscript.setText(document.getElementById('el'));
 // you will see "hello" in the element
 </script>
 ```
@@ -110,7 +110,7 @@ Relative paths in node modules are resolved according to path of that module (li
 
 ## Mixed Context Mode
 
-Mixed context is introduced in NW.js 0.13. When running NW.js with [`--mixed-context` CLI option](../../References/Command Line Options.md#mixedcontext), a new Node context is created at the time of each browser context creation and running in a same context as browser context, a.k.a. the Mixed context.
+Mixed context is introduced in NW.js 0.13. When running NW.js with [`--mixed-context` CLI option](../../References/Command Line Options.md#-mixed-context), a new Node context is created at the time of each browser context creation and running in a same context as browser context, a.k.a. the Mixed context.
 
 ### Load Script in Mixed Context Mode
 
diff --git a/docs/References/Window.md b/docs/References/Window.md
@@ -126,7 +126,7 @@ Get or set the page zoom. `0` for normal size; positive value for zooming in; ne
 
 ## win.cookies.*
 
-This includes multiple functions to manipulate the cookies. The API is defined in the same way as [Chrome Extensions'](http://developer.chrome.com/extensions/cookies.html). NW.js supports the `get`, `getAll`, `remove` and `set` methods; `onChanged` event (supporting both `addListener` and `removeListener` function on this event).
+This includes multiple functions to manipulate the cookies. The API is defined in the same way as [Chrome Extensions](http://developer.chrome.com/extensions/cookies.html). NW.js supports the `get`, `getAll`, `remove` and `set` methods; `onChanged` event (supporting both `addListener` and `removeListener` function on this event).
 
 And anything related to `CookieStore` in the Chrome extension API is not supported, because there is only one global cookie store in NW.js apps.
 
@@ -571,7 +571,7 @@ Emitted when window leaves fullscreen state.
 
 ## Event: zoom
 
-Emitted when window zooming changed. It has a parameter indicating the new zoom level. See [`win.zoom()` method](#winzoom) for the parameter's value definition.
+Emitted when window zooming changed. It has a parameter indicating the new zoom level. See [`win.zoom()` method](#winzoomlevel) for the parameter's value definition.
 
 ## Event: capturepagedone
 
