earlier replies
Replying to @koutsiaris @brave
Cc: @BraveSampson
1
1
Taking a look now.
1
The differences are subtle, but I am able to confirm the issue. Here's a side-by-side with RGB values. Left is Brave. Right is Edge.
1
1
GIF
Looks like @vivaldibrowser and Chrome produce the same color as @brave (on my machine). Checking a few more things.
1
Top to bottom: Brave (c62), Vivaldi (c61), Chrome (c62), and Edge. The first 3 are in unison regarding the on-screen pixels. Maybe hardware.
2
GIF
Wow, I was on Chrome 61 and after updating to 62 colors appear the same. There is a visible difference with @MSEdgeDev and @firefox
1
1
3
Looks like a similar issue (to the one @ericlaw referenced) was also filed against the Edge team—closed as wont-fix. developer.microsoft.com/en-u…
1
1
The great thing about web standards is.... Cc @davidbaron
1
4
Sounds like something related to support (or not) for color management.
1
2
No normative spec ensuring interop?
1
Replying to @BrendanEich @BraveSampson @koutsiaris @brave @vivaldibrowser @MSEdgeDev @firefox @ericlaw
It's been normative since at least a decade before anyone followed it...

Oct 30, 2017 · 8:06 PM UTC

1
3