If by style, you mean code formatting, try to automate it. I mean the formatting. In the long run, it takes less time than fighting over it.
In a code review, probably the most important thing is to make sure that it is always about the code and never about the person. If you have that, you are on the good path to meaningful discussions.
Hopefully other people in the team ask themselves the same questions you asked and replies should be noted and probably they should be part of the code review guidelines in your teams.
I elaborated a bit more on this topic in a post, you might find it interesting:
If by style, you mean code formatting, try to automate it. I mean the formatting. In the long run, it takes less time than fighting over it.
In a code review, probably the most important thing is to make sure that it is always about the code and never about the person. If you have that, you are on the good path to meaningful discussions.
Hopefully other people in the team ask themselves the same questions you asked and replies should be noted and probably they should be part of the code review guidelines in your teams.
I elaborated a bit more on this topic in a post, you might find it interesting:
Sane office environment with code review guidelines
Sandor Dargo ・ Mar 28 '18 ・ 6 min read