<ul dir="auto">
<li>Electron Version: 2.0.0</li>
<li>Operating System (Platform and Version): windows 8.1</li>
<li>Last known working Electron version: none</li>
</ul>
<p dir="auto"><strong>Expected Behavior</strong><br>
I create a browerwindow with frame: false and transparent: true, when i use maximize(), i need the event 'maximize' and isMaximized() return true.</p>
<p dir="auto"><strong>Actual behavior</strong><br>
no event emited, and isMaximize() return false.</p>
<p dir="auto">Currently, the <em>bluetooth-select-device</em> event is within the main process. If the user wants to mimick standard WebBluetooth behavior, the renderer process needs to display a dialog.</p>
<p dir="auto">Also, receiving a long list of devices (with many duplicates!) is not user-friendly. The user needs to see devices as they are found. Often, a devices is found only after turning it off and on again.</p>
<p dir="auto">Following suggestion: Implement <em>bluetooth-select-device</em> on the renderer side, with a single argument, the callback.</p>
<p dir="auto">Implement a <em>bluetooth-device-found</em> event; its argument should be a standard BluetoothDevice instance with an "id" property instead of a "deviceId" property.</p>
<p dir="auto">The user could display an empty dialog on the former event and remember the callback. On the latter events, the user would fill the dialog.</p>
<p dir="auto">The dialog could event become part of the standard Electron package. See, for example, the file DeviceChooserUI.js in the web-bluetooth-polyfill package for an implementation.</p>
<ul dir="auto">
<li>Electron version: 1.7.8</li>
<li>Operating system: Mac OS 10.12.6</li>
</ul>