Chrome 62 adds a default border radius to <button>

[morkro]

Hello,

I have just updated to Chrome 62.0.3202.62 and discovered that they've added a default border radius of 4px to all <button> and input[type="button"]. Is this something normalize.css should normalize from now on?

Screenshot:

[slavanga]

This is interesting. I noticed two things:

1. The user agent stylesheet only changed on macOS. This makes sense because Windows generally doesn’t have round buttons.
2. Even on macOS no border-radius is applied because of line 281.

[morkro]

2. Even on macOS no border-radius is applied because of line 281.

I can't confirm. Even with -webkit-appearance: button; they still have a rounded border in Chrome.

[kostasmanionis]

For reference: https://www.chromestatus.com/features/5743649186906112

[mgol]

A ticket about that that got wontfixed: https://bugs.chromium.org/p/chromium/issues/detail?id=752450

IMO it'd be good for normalize to reset border-radius on buttons. Note that people may set -webkit-appearance: none in their code for a specific button and they won't know their button now looks broken in Chrome for macOS (and only there). This sounds like a kind of thing that normalize.css should handle.

[adamduncan]

PR for this issue here if it helps: #697

[tmair]

The chrome team decided to revert the change: https://bugs.chromium.org/p/chromium/issues/detail?id=752450#c13

[cannikin]

So I just got upgraded to Chrome 62 and all our buttons got rounded! I'm on macOS. See the two buttons on the right here (the first three are actually forms, not buttons):

Here's the computed style:

[coreation]

Any idea on what the gap is between them deciding to revert the change and actual chrom(ium) updates?

[mgol]

@coreation It'll be included in Chrome 63, tentatively scheduled for Dec 5th. See https://www.chromium.org/developers/calendar

[hay]

It seems the Chrome team has already (wisely IMO) decided to revert this change. Starting with Chrome 63 buttons will have no border-radius again.

[garrettw]

@hay If you had read the comments here before posting your own, you’d have realized that you’d be simply repeating what has already been mentioned.

[hay]

@garrettw i read the comments before posting myself, i just didn't see it. But thanks for pointing that out.

[mgol]

Chrome 63 has just been released.

[danielbarillo]

I can confirm that updating Chrome from 62 to 63 fixes this issue!

[mgol]

Should it be closed?

[necolas]

Thanks for the info