Warning on titlebarAppearsTransparent when setting frame: false or titleBarStyle: hidden

[caesarsol]

This is still a problem as of 2.0.0, as described in these (now closed) issues: #11150
#11169
#11743

The warning is:

Electron *** WARNING: Textured window <AtomNSWindow: 0x7fe3687673e0> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

Electron version: 2.0.0
Operating system: Mac OS 10.13.4

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[alanning]

For a reproduction of this issue, please run the framless-window sample electron app located here:

https://github.com/hokein/electron-sample-apps/tree/master/frameless-window

Reproduction steps:
(assumes yarn already installed)

$ cd ~/tmp
$ git clone https://github.com/hokein/electron-sample-apps
$ cd electron-sample-apps
$ yarn add electron
$ npx electron --version
v2.0.0
$ npx electron frameless-window
2018-05-13 15:07:44.376 Electron[42121:6477918] *** WARNING: Textured window <AtomNSWindow: 0x7fd0f473fa00> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

[joernroeder]

any updates on this?

[ckerr]

Using the test case provided in #12814 (comment) I can confirm this still exists in Electron 2.0.5.

It's also not a Mac-specific issue; I'm also seeing it on Ubuntu Linux

[codebytere]

This no longer occurs on 3-0-x, I've confirmed with the repro steps!

[Nantris]

@codebytere I'm still seeing this with Electron@3.0.0 on macOS 10.13.2 with frame: false and all other BrowserWindow options left to defaults.

2018-10-01 18:06:06.072 Electron[39479:673750] *** WARNING: Textured window <AtomNSWindow: 0x7f8594f3c000> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

Edit: Same warning with Electron@3.0.2 following the steps outlined by @alanning.

[jjshankar]

Reproducible on Electron 3.0.5 - MacOS High Sierra 10.13.6.

I can still repro this with either of the options: frame :false or titleBarStyle: "hidden"

A previously recommended fix to include backgroundColor: "#fff" did not work.

[BinaryMuse]

When running an example through Fiddle, even with the latest Electron beta (4.0.0-beta.4), I can reproduce the issue, but as soon as I try to do so with a local debug build off master the issue disappears. Needs some more investigation 🔍

[BinaryMuse]

On a hunch, I built a release version of Electron (and got my lap nice and toasty) but I'm also unable to reproduce with this. Very strange.

I wonder if this could have something to do with the SDK we link against for release builds? I checked with @MarshallOfSound and we link against 10.12 currently (I'm linking against 10.13).

[wuwb]

Reproducible on Electron 4.0.1

[geakstr]

Still exists in 4.0.4

[meizikeai]

Still exists in 4.0.6

[solidgoldpig]

Still exists in 4.1.0

[cxdy]

Not working for me either.

// my window
  window = new BrowserWindow({
    width: 300,
    height: 450,
    show: false,
    frame: false,
    fullscreenable: false,
    webPreferences: {
      backgroundThrottling: false
    }
  })

Software versions:

Electron - v4.16.0
Node - v10.15.1
OS - macOS 10.14.3

[Nantris]

@cxdy there's no Electron@4.16.0 right now that I'm aware of.

[cxdy]

@slapbox that's just the version NPM gave me

[BenjaminHoegh]

@slapbox that's just the version NPM gave me

NPM gives me v5.0.0 so I'm also confuse, still got the error tho

[varave]

Still exists in 5.0.1

[limichange]

Still exists in 5.0.4

[mattpilott]

5.0.6 too 😔

[mechamogeo]

v6.0.0 too 😥

[BenjaminHoegh]

Why are they not fixing this issue!

[varave]

@BenjaminHoegh I think because it is not the highest priority

[zcbenz]

This problem should have been fixed at least for Electron >= 9.