This is Windows:

This is Google on Windows:

Google won't fix this.
Could you clarify what you mean by "arbitrary"? Additionally, what specifically do you consider to be "Windows native style"?
For my curiosity, do you mind posting a source to your claim that Google won't change this?
You should obey the system's style guide.
Use Windows's default style, instead of implement your own.
Specification: https://msdn.microsoft.com/en-us/library/windows/desktop/dn742392.aspx
Google won't change this: https://superuser.com/a/630510
@zcyzcy88 If you're looking for UI consistency, then Windows is not the operating system to go for, considering that Windows 10 UI alone has several different context menus.
My knowledge on this is limited, but I believe Chrome uses its own rendering engine for its UI. It also has a consistent UI across all of its desktop platforms. So changing the context menu style may not be trivial.
@Artur96 You are true, but Chrome is even not consistency inside self.


@Eloston Bad argument.
Chrome uses its own rendering engine for its UI.
Gecko (Firefox engine) also, but Gecko did it.
It also has a consistent UI across all of its desktop platforms.
False. Chrome obey the standard on Mac.
@zcyzcy88 Regarding your images, it's possible the context menu in the top image is from the title bar. The title bar might be rendered by Windows, not Chrome, so the style would be different.
EDIT: wouldn't -> would
I just want to pitch in to say that this might be out of scope for this project, whose goal is to remove Google's spyware from Chromium. If you want to mess with the UI design, you should maintain a separate patchset for that.
Just my two cents.
@Streetwalrus You are correct, but I would be fine with it if someone is able to continually maintain such patch and it doesn't interfere with main development (within reason). The motivations of this project describe the core changes I want in a Chromium browser, but I don't mind other changes if they don't deviate too far from how Chromium looks and behaves.
This issue should be closed.
Most helpful comment
I just want to pitch in to say that this might be out of scope for this project, whose goal is to remove Google's spyware from Chromium. If you want to mess with the UI design, you should maintain a separate patchset for that.
Just my two cents.