-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
browser/api/lib/window.coffee #3
Comments
I agree that the name |
zcbenz
pushed a commit
that referenced
this issue
Sep 11, 2015
Closed
kevinsawicki
pushed a commit
that referenced
this issue
May 9, 2017
We deduce the name of the application from the CFBundleName of the .app bundle and use a path based on that. Similar logic should be implementable for other platforms. Fixes #3.
kevinsawicki
pushed a commit
that referenced
this issue
May 9, 2017
We deduce the name of the application from the CFBundleName of the .app bundle and use a path based on that. Similar logic should be implementable for other platforms. Fixes #3.
5 tasks
sentialx
added a commit
to sentialx/electron
that referenced
this issue
Apr 8, 2021
This was referenced Dec 16, 2021
3 tasks
3 tasks
This was referenced Aug 16, 2023
This was referenced Aug 17, 2023
This was referenced Sep 6, 2023
This was referenced Sep 19, 2023
This was referenced Oct 3, 2023
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What do you think about renaming window.coffee to something else? The reason is it is confusing to have the DOM
window
object and to have the OSwindow
object. We could call itbrowserWindow
oratomWindow
or you can convince me that we should keep it calledwindow
.The text was updated successfully, but these errors were encountered: