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
chore: remove macOS 10.9 specific code #15174
Conversation
20dfcc9
to
a08be1b
Compare
@MarshallOfSound can you please review? |
a08be1b
to
f5944df
Compare
shell_->fullscreen_window_title())) { | ||
[window setTitleVisibility:NSWindowTitleVisible]; | ||
} | ||
// For frameless window we don't show set title for normal mode since the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm concerned that this diff still shows with w=1
(ignore whitespace changes).
Can you verify that the line endings and tabs vs spaces haven't changed in this section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MarshallOfSound SourceTree shows this properly. I did check it and I am not changing newlines and/or indentation (tabs vs. spaces)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tentatively approved pending a check of line endings in one file
f5944df
to
39bef61
Compare
39bef61
to
ab342f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking review because I don't think we should be changing the deployment target in Chromium.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch @nornagon Missed that patch completely as the diff was minimized,
@MarshallOfSound if we are not comfortable with changing Chromium’s deployment target, then I will just close this PR and re-open again when we update to a version, which does change it to 10.10 There are a few changes that can be done without bumping the deployment target, but I think all the cleanup should probably be done together. |
Description of Change
Follow up to #15357.
Bump the macOS deployment target to 10.10 and remove macOS 10.9 specific code.
Checklist
npm test
passesRelease Notes
Notes: macOS deployment target bumped to 10.10.