105 lines
3.8 KiB
Markdown
105 lines
3.8 KiB
Markdown
# Frameless Window
|
|
|
|
A frameless window is a window that has no [chrome](https://developer.mozilla.org/en-US/docs/Glossary/Chrome), the parts of the window, like toolbars, that are not a part of the web page. These are options on the [`BrowserWindow`](browser-window.md) class.
|
|
|
|
## Create a frameless window
|
|
|
|
To create a frameless window, you need to set `frame` to `false` in
|
|
[BrowserWindow](browser-window.md)'s `options`:
|
|
|
|
|
|
```javascript
|
|
const BrowserWindow = require('electron').BrowserWindow;
|
|
var win = new BrowserWindow({ width: 800, height: 600, frame: false });
|
|
```
|
|
|
|
### Alternatives on OS X
|
|
|
|
On Mac OS X 10.10 Yosemite and newer, there's an alternative way to specify
|
|
a chromeless window. Instead of setting `frame` to `false` which disables
|
|
both the titlebar and window controls, you may want to have the title bar
|
|
hidden and your content extend to the full window size, yet still preserve
|
|
the window controls ("traffic lights") for standard window actions.
|
|
You can do so by specifying the new `title-bar-style` option:
|
|
|
|
```javascript
|
|
var win = new BrowserWindow({ 'title-bar-style': 'hidden' });
|
|
```
|
|
|
|
## Transparent window
|
|
|
|
By setting the `transparent` option to `true`, you can also make the frameless
|
|
window transparent:
|
|
|
|
```javascript
|
|
var win = new BrowserWindow({ transparent: true, frame: false });
|
|
```
|
|
|
|
### Limitations
|
|
|
|
* You can not click through the transparent area. We are going to introduce an
|
|
API to set window shape to solve this, but currently blocked at an
|
|
[upstream bug](https://code.google.com/p/chromium/issues/detail?id=387234).
|
|
* Transparent windows are not resizable. Setting `resizable` to `true` may make
|
|
a transparent window stop working on some platforms.
|
|
* The `blur` filter only applies to the web page, so there is no way to apply
|
|
blur effect to the content below the window (i.e. other applications open on
|
|
the user's system).
|
|
* On Windows operation systems, transparent windows will not work when DWM is
|
|
disabled.
|
|
* On Linux users have to put `--enable-transparent-visuals --disable-gpu` in
|
|
the command line to disable GPU and allow ARGB to make transparent window,
|
|
this is caused by an upstream bug that [alpha channel doesn't work on some
|
|
NVidia drivers](https://code.google.com/p/chromium/issues/detail?id=369209) on
|
|
Linux.
|
|
* On Mac the native window shadow will not be shown on a transparent window.
|
|
|
|
## Draggable region
|
|
|
|
By default, the frameless window is non-draggable. Apps need to specify
|
|
`-webkit-app-region: drag` in CSS to tell Electron which regions are draggable
|
|
(like the OS's standard titlebar), and apps can also use
|
|
`-webkit-app-region: no-drag` to exclude the non-draggable area from the
|
|
draggable region. Note that only rectangular shapes are currently supported.
|
|
|
|
To make the whole window draggable, you can add `-webkit-app-region: drag` as
|
|
`body`'s style:
|
|
|
|
```html
|
|
<body style="-webkit-app-region: drag">
|
|
</body>
|
|
```
|
|
|
|
And note that if you have made the whole window draggable, you must also mark
|
|
buttons as non-draggable, otherwise it would be impossible for users to click on
|
|
them:
|
|
|
|
```css
|
|
button {
|
|
-webkit-app-region: no-drag;
|
|
}
|
|
```
|
|
|
|
If you're setting just a custom titlebar as draggable, you also need to make all
|
|
buttons in titlebar non-draggable.
|
|
|
|
## Text selection
|
|
|
|
In a frameless window the dragging behaviour may conflict with selecting text.
|
|
For example, when you drag the titlebar you may accidentally select the text on
|
|
the titlebar. To prevent this, you need to disable text selection within a
|
|
draggable area like this:
|
|
|
|
```css
|
|
.titlebar {
|
|
-webkit-user-select: none;
|
|
-webkit-app-region: drag;
|
|
}
|
|
```
|
|
|
|
## Context menu
|
|
|
|
On some platforms, the draggable area will be treated as a non-client frame, so
|
|
when you right click on it a system menu will pop up. To make the context menu
|
|
behave correctly on all platforms you should never use a custom context menu on
|
|
draggable areas.
|