![]() This has now been fixed (see #37210 for discussion).Īs a result, if your app uses a frameless window with draggable regions on macOS, the regions which are draggable in your app may change in Electron 23. Beginning in Electron 23, a drag region on top of a no-drag region will correctly cause the region to be draggable.Īdditionally, the customButtonsOnHover BrowserWindow property previously created a draggable region which ignored the -webkit-app-region CSS property. That is, if a drag region was above a no-drag region, it would be ignored. Previously, when a region with -webkit-app-region: no-drag overlapped a region with -webkit-app-region: drag, the no-drag region would always take precedence on macOS, regardless of CSS layering. The implementation of draggable regions (using the CSS property -webkit-app-region: drag) has changed on macOS to bring it in line with Windows and Linux. Planned Breaking API Changes (23.0) Behavior Changed: Draggable Regions on macOS Which accepts null instead of to reset the position to Removed: tTrafficLightPosition(position) ītTrafficLightPosition(position) has been removed, theītWindowButtonPosition(position) API should be used instead ![]() In the BrowserWindow for all WebContents displayed by it. WebContents.backgroundThrottling set to false will disable frames throttling Planned Breaking API Changes (28.0) Behavior Changed: WebContents.backgroundThrottling set to false affects all WebContents in the host BrowserWindow Removed: An API or feature was removed, and is no longer supported by Electron.The API will continue to function, but will emit a deprecation warning, and will be removed in a future release. Deprecated: An API was marked as deprecated. ![]() The old behavior can be restored by explicitly specifying the value.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |