Tested this issue on reported chrome version 68.0.3440.75 using Windows 10. Attaching screen-cast for reference.
Steps: 
---------
1. Launched reported chrome and M-67
2. Navigated given URL's 
As we are observed that same behavior on both chrome(M-67 & M6-8) and Firefox browsers

@Reporter: Could you please review the attached screen-cast and confirm if anything being missed here.

Thanks..!

Deleted: 869115.mp4 4.7 MB

	869115.mp4 4.7 MB View Download

This issue seems similar to  Issue 847024 . Hence CC'ing Dev for further inputs.


Thanks..!

Attached are screenshots of the red pen on my desktop in Firefox and Chrome 68 (I don't know how to revert to 67). Even in the thumbnails I can see that the Chrome 68 png is darker.

Deleted: firefox_red.png 21.4 KB

	firefox_red.png 21.4 KB View Download

Deleted: chrome68_red.png 22.1 KB

	chrome68_red.png 22.1 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The differences might seem subtle if not compared side by side. But they are really very big differences considering the source markup and color range. Colors that used to be dark red are now simply black. My codepen illustrates hex 10-1F because 00 through 0F is almost totally black now.

This looks like your monitor color profile is altering those colors, although if you changed the Force Color Profile setting, that should fix it. After changing the Force Color Profile to sRGB, did you close all Chrome windows and restart Chrome? (That setting only takes effect on a fresh launch of Chrome).

Also, in Firefox, what happens if you go to about:config, then search for 'gfx.color_management.mode', and change it from 2 (the default), to 1? By default, Firefox only does color management of some images (a very small percentage of images, in fact). Mode 1 enables full color management of all content. On my system, Chrome and Firefox do render those pens differently, until I switched Firefox to mode 1, at which point they look identical.

I followed the instructions for Force Color Profile to the letter, no change.
I can change these settings in Firefox, but that's not the point. I loaded my web page in Chrome one morning last week and the colors were changed because Chrome had installed v68. What happened? Firefox and Chrome 67 look the same, Firefox and Chrome 68 do not.
The default rendering changed in 68, and it changed in a way that makes it non-conforming with other browsers. That is a problem for all web pages.

How can a developer or graphic artist produce a web page that renders the same colors in all the different browsers, on all the different hardware? Sure, there might be some subtle differences, but these Chrome 68 differences in the dark range are not subtle. Dark blues on my page became gray, devoid of color altogether.

Sorry, I was suggesting the FF change mostly to diagnose what's happening on your machine - not as a "fix". I'm running both m68 and m70 locally, and those gradients look fine to me (slightly different from default Firefox because I have a color profile installed for my monitor, but nowhere near as dark as you're seeing). I'm trying to determine if it's an issue with your color profile, or something else related to color or SVG. Do you mind attaching the contents of chrome://gpu? That lets us know if you're using CPU or GPU rasterization, and has information about your monitor's color profile.

Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
Driver Bug Workarounds
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_discard_framebuffer
disable_framebuffer_cmaa
exit_on_context_lost
force_cube_complete
msaa_is_slow
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
Problems Detected
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Applied Workarounds: msaa_is_slow
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Don't expose disjoint_timer_query extensions to WebGL: 808744
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Viz service display compositor is not enabled by default.
Disabled Features: viz_display_compositor
Skia renderer is not used by default.
Disabled Features: skia_renderer
Skia deferred display list is not used by default.
Disabled Features: skia_deferred_display_list
Version Information
Data exported	2018-07-31T14:20:58.165Z
Chrome version	Chrome/68.0.3440.75
Operating system	Windows NT 10.0.17134
Software rendering list URL	https://chromium.googlesource.com/chromium/src/+/cf598d63a4f1b9e7cd14f2a8433276b196e3e07d/gpu/config/software_rendering_list.json
Driver bug list URL	https://chromium.googlesource.com/chromium/src/+/cf598d63a4f1b9e7cd14f2a8433276b196e3e07d/gpu/config/gpu_driver_bug_list.json
ANGLE commit id	ba1627086779
2D graphics backend	Skia/68 7d479192f0bf2a2f0e872d40e3fe3ce9978bf3cc-
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --enable-features=NewAudioRenderingMixingStrategy --disable-features=Windows10CustomTitlebar --flag-switches-end
Driver Information
Initialization time	261
In-process GPU	false
Passthrough Command Decoder	false
Direct Composition	true
Supports overlays	true
Sandboxed	true
GPU0	VENDOR = 0x8086 [Google Inc.], DEVICE= 0x5912 [ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0)] *ACTIVE*
Optimus	false
AMD switchable	false
Desktop compositing	Aero Glass
Diagonal Monitor Size of \\.\DISPLAY2	23.9"
Diagonal Monitor Size of \\.\DISPLAY1	20.0"
Driver D3D12 feature level	D3D 12.1
Driver Vulkan API version	Vulkan API 1.0.0
Driver vendor	Intel Corporation
Driver version	23.20.16.4973
Driver date	2-28-2018
Pixel shader version	5.0
Vertex shader version	5.0
Max. MSAA samples	16
Machine model name	
Machine model version	
GL_VENDOR	Google Inc.
GL_RENDERER	ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0)
GL_VERSION	OpenGL ES 2.0 (ANGLE 2.1.0.ba1627086779)
GL_EXTENSIONS	GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Disabled WebGL Extensions	EXT_disjoint_timer_query EXT_disjoint_timer_query_webgl2
Window system binding vendor	Google Inc. (adapter LUID: 000000000000c692)
Window system binding version	1.4 (ANGLE 2.1.0.ba1627086779)
Window system binding extensions	EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled
Direct rendering	Yes
Reset notification strategy	0x8252
GPU process crash count	0
Compositor Information
Tile Update Mode	One-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
ATC	Software only
ATCIA	Software only
DXT1	Software only
DXT5	Software only
ETC1	Software only
R_8	Software only
R_16	Software only
RG_88	Software only
BGR_565	Software only
RGBA_4444	Software only
RGBX_8888	GPU_READ, SCANOUT
RGBA_8888	GPU_READ, SCANOUT
BGRX_8888	Software only
BGRX_1010102	Software only
RGBX_1010102	Software only
BGRA_8888	Software only
RGBA_F16	Software only
YVU_420	Software only
YUV_420_BIPLANAR	Software only
UYVY_422	Software only
Display(s) Information
Info	Display[2528732444] bounds=[1920,0 1600x1200], workarea=[1920,0 1600x1200], scale=1, external.
Color space information	{primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL}
Bits per color component	8
Bits per pixel	24
Info	Display[2779098405] bounds=[0,0 1920x1080], workarea=[0,0 1920x1080], scale=1, external.
Color space information	{primaries_d50_referred: [[0.6580, 0.3280], [0.3149, 0.6029], [0.1503, 0.0910]], transfer:0.1895*x + 0.0000 if x < 0.2500 else (0.9994*x + 0.0006)**2.2016 + -0.0001, matrix:RGB, range:FULL}
Bits per color component	8
Bits per pixel	24
Video Acceleration Information
Decode h264 baseline	up to 4096x2304 pixels
Decode h264 baseline	up to 2304x4096 pixels
Decode h264 main	up to 4096x2304 pixels
Decode h264 main	up to 2304x4096 pixels
Decode h264 high	up to 4096x2304 pixels
Decode h264 high	up to 2304x4096 pixels
Decode vp8	up to 7680x4320 pixels
Decode vp8	up to 4320x7680 pixels
Decode vp9 profile0	up to 7680x4320 pixels
Decode vp9 profile0	up to 4320x7680 pixels
Decode vp9 profile1	up to 7680x4320 pixels
Decode vp9 profile1	up to 4320x7680 pixels
Decode vp9 profile2	up to 7680x4320 pixels
Decode vp9 profile2	up to 4320x7680 pixels
Decode vp9 profile3	up to 7680x4320 pixels
Decode vp9 profile3	up to 4320x7680 pixels
Encode h264 baseline	up to 3840x2176 pixels and/or 30.000 fps
Encode h264 main	up to 3840x2176 pixels and/or 30.000 fps
Encode h264 high	up to 3840x2176 pixels and/or 30.000 fps
Diagnostics
0
b3DAccelerationEnabled	true
b3DAccelerationExists	true
bAGPEnabled	true
bAGPExistenceValid	true
bAGPExists	true
bCanRenderWindow	true
bDDAccelerationEnabled	true
bDriverBeta	false
bDriverDebug	false
bDriverSigned	false
bDriverSignedValid	false
bNoHardware	false
dwBpp	32
dwDDIVersion	12
dwHeight	1200
dwRefreshRate	60
dwWHQLLevel	0
dwWidth	1600
iAdapter	1
lDriverSize	1905744
lMiniVddSize	0
szAGPStatusEnglish	Enabled
szAGPStatusLocalized	Enabled
szChipType	Intel(R) HD Graphics Family
szD3DStatusEnglish	Enabled
szD3DStatusLocalized	Enabled
szDACType	Internal
szDDIVersionEnglish	12
szDDIVersionLocalized	12
szDDStatusEnglish	Enabled
szDDStatusLocalized	Enabled
szDXVAHDEnglish	Supported
szDXVAModes	ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
szDescription	Intel(R) HD Graphics 630
szDeviceId	0x5912
szDeviceIdentifier	{D7B78E66-1A52-11CF-8564-10F0BFC2DA35}
szDeviceName	\\.\DISPLAY1
szDisplayMemoryEnglish	4180 MB
szDisplayMemoryLocalized	4180 MB
szDisplayModeEnglish	1600 x 1200 (32 bit) (60Hz)
szDisplayModeLocalized	1600 x 1200 (32 bit) (60Hz)
szDriverAssemblyVersion	23.20.16.4973
szDriverAttributes	Final Retail
szDriverDateEnglish	2/27/2018 6:00:00 PM
szDriverDateLocalized	2/27/2018 18:00:00
szDriverLanguageEnglish	English
szDriverLanguageLocalized	English
szDriverModelEnglish	WDDM 2.3
szDriverModelLocalized	WDDM 2.3
szDriverName	C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd12umd64.dll
szDriverNodeStrongName	oem3.inf:5f63e5341bf86c41:iKBLD_w10_DS:23.20.16.4973:pci\ven_8086&dev_5912
szDriverSignDate	Unknown
szDriverVersion	23.20.0016.4973
szKeyDeviceID	Enum\PCI\VEN_8086&DEV_5912&SUBSYS_D0001458&REV_04
szKeyDeviceKey	\Registry\Machine\System\CurrentControlSet\Control\Video\{41C0C22C-4DFE-11E8-A3A1-85DD61D9EF5A}\0000
szManufacturer	Intel Corporation
szMiniVdd	unknown
szMiniVddDateEnglish	Unknown
szMiniVddDateLocalized	unknown
szMonitorMaxRes	Unknown
szMonitorName	Generic PnP Monitor
szNotesEnglish	No problems found.
szNotesLocalized	No problems found.
szOverlayEnglish	Supported
szRankOfInstalledDriver	00D12001
szRegHelpText	Unknown
szRevision	Unknown
szRevisionId	0x0004
szSubSysId	0xD0001458
szTestResultD3D7English	Not run
szTestResultD3D7Localized	Not run
szTestResultD3D8English	Not run
szTestResultD3D8Localized	Not run
szTestResultD3D9English	Not run
szTestResultD3D9Localized	Not run
szTestResultDDEnglish	Not run
szTestResultDDLocalized	Not run
szVdd	unknown
szVendorId	0x8086
1
b3DAccelerationEnabled	true
b3DAccelerationExists	true
bAGPEnabled	true
bAGPExistenceValid	true
bAGPExists	true
bCanRenderWindow	true
bDDAccelerationEnabled	true
bDriverBeta	false
bDriverDebug	false
bDriverSigned	false
bDriverSignedValid	false
bNoHardware	false
dwBpp	32
dwDDIVersion	12
dwHeight	1080
dwRefreshRate	59
dwWHQLLevel	0
dwWidth	1920
iAdapter	0
lDriverSize	1905744
lMiniVddSize	0
szAGPStatusEnglish	Enabled
szAGPStatusLocalized	Enabled
szChipType	Intel(R) HD Graphics Family
szD3DStatusEnglish	Enabled
szD3DStatusLocalized	Enabled
szDACType	Internal
szDDIVersionEnglish	12
szDDIVersionLocalized	12
szDDStatusEnglish	Enabled
szDDStatusLocalized	Enabled
szDXVAHDEnglish	Supported
szDXVAModes	ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
szDescription	Intel(R) HD Graphics 630
szDeviceId	0x5912
szDeviceIdentifier	{D7B78E66-1A52-11CF-8564-10F0BFC2DA35}
szDeviceName	\\.\DISPLAY2
szDisplayMemoryEnglish	4180 MB
szDisplayMemoryLocalized	4180 MB
szDisplayModeEnglish	1920 x 1080 (32 bit) (59Hz)
szDisplayModeLocalized	1920 x 1080 (32 bit) (59Hz)
szDriverAssemblyVersion	23.20.16.4973
szDriverAttributes	Final Retail
szDriverDateEnglish	2/27/2018 6:00:00 PM
szDriverDateLocalized	2/27/2018 18:00:00
szDriverLanguageEnglish	English
szDriverLanguageLocalized	English
szDriverModelEnglish	WDDM 2.3
szDriverModelLocalized	WDDM 2.3
szDriverName	C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igd12umd64.dll
szDriverNodeStrongName	oem3.inf:5f63e5341bf86c41:iKBLD_w10_DS:23.20.16.4973:pci\ven_8086&dev_5912
szDriverSignDate	Unknown
szDriverVersion	23.20.0016.4973
szKeyDeviceID	Enum\PCI\VEN_8086&DEV_5912&SUBSYS_D0001458&REV_04
szKeyDeviceKey	\Registry\Machine\System\CurrentControlSet\Control\Video\{41C0C22C-4DFE-11E8-A3A1-85DD61D9EF5A}\0001
szManufacturer	Intel Corporation
szMiniVdd	unknown
szMiniVddDateEnglish	Unknown
szMiniVddDateLocalized	unknown
szMonitorMaxRes	Unknown
szMonitorName	BenQ RL2455
szNotesEnglish	No problems found.
szNotesLocalized	No problems found.
szOverlayEnglish	Supported
szRankOfInstalledDriver	00D12001
szRegHelpText	Unknown
szRevision	Unknown
szRevisionId	0x0004
szSubSysId	0xD0001458
szTestResultD3D7English	Not run
szTestResultD3D7Localized	Not run
szTestResultD3D8English	Not run
szTestResultD3D8Localized	Not run
szTestResultD3D9English	Not run
szTestResultD3D9Localized	Not run
szTestResultDDEnglish	Not run
szTestResultDDLocalized	Not run
szVdd	unknown
szVendorId	0x8086
Log Messages
[7864:10592:0731/070021.896:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(102,7-62): warning X3557: loop only executes for 1 iteration(s), consider removing [loop]
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.

...and changing my Firefox color mode to 1 has the same effect that you describe, if that helps your diagnosis. The colors are now aligned with the darker Chrome 68 colors.

Interesting. Your left monitor has a very odd color profile - I'm guessing it was calibrated? The gamut looks good (bigger than sRGB, not quite Adobe or P3). The transfer curve (which affects how bright things appear as the colors we output go from 0 - 255) is extremely bright at the low end, though. The attached image shows the light level for a given color with sRGB (which is typical) in purple, and your monitor's profile in orange.

So: New theory. Other issues were caused because the new profile parser started accepting profiles that were previously rejected, causing color management to start happening, and alter what people saw. It's possible here that the new profile parser started *rejecting* your monitor profile, causing us to always use sRGB. If we did use your monitor profile, Chrome would make dark colors brighter to compensate, and if your monitor really has that strange response, then dark colors would be quite dark if we failed to do so.

Even if you don't want to change it, can you go look at Firefox's 'gfx.color_management.mode' setting? This explanation doesn't make sense unless that's already set to 1, as far as I can tell.

Also, if you can attach your actual ICC profile for your monitor, that would be helpful - we can directly check to see if our code is rejecting it (and why!). In the Windows start menu, type 'Color Management'. That will bring up a control panel color management screen. In the Device drop-down, pick your left monitor (Identify Monitors will let you know which is 1 and which is 2). In the list of 'Profiles associated with this device', there will be one or more files listed. Whichever one is marked as "(default)" is the one we want. The actual file is probably located in C:\windows\system32\spool\drivers\color.

There are screenshots of most of that in this docuemnt: https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/view#heading=h.fdpe4jqn1eyl

Deleted: transfer_functions.png 70.7 KB

	transfer_functions.png 70.7 KB View Download

Ah, sorry - I was in the middle of writing my note when you posted your last comment. Hmm. Now I'm back to being confused. If you can attach the profile, that's still going to be helpful. We need to think about this a bit...

Attached is the file you seek.  It is the only file for that monitor.  It is my main monitor in standard HD. The other monitor is running VGA and acts as a debugging console for the most part.

I have been a software developer for too many years now, but I am a relatively newbie when it comes to coding graphics for SVG/HTML. Thanks for all the detailed information. This configuration is one of the standard ones that came with this BenQ monitor.  I picked one from the list when I installed the monitor a couple of years ago.

Deleted: RL2455.icm 100 KB

RL2455.icm 100 KB Download

Okay. I made a math error there, I'm 99% certain that force-color-profile will fix this. I'm guessing that some Chrome process stuck around (maybe not even a visible window), such that "re-starting" chrome didn't actually re-set the profile we use.

Once you're sure that you've set force-color-profile to sRGB, can you try restarting your machine (or at least signing out of windows and back in)? Given the contents of that profile, and that Firefox exhibits the same behavior once it's color managing SVG, that would all make sense.

The colors are brighter, but still they are changed from 67.  I have attached an updated png of the colors in Chrome with force-color-profile set to sRGB, and post-reboot.
As I look at my web page and change the dark blue back from my v68-adjusted value of #000024 to the original #000010, the original color is still washed out in 68, still dark gray with no hint of blue. 10 is the lowest value in these codepens. You can adjust the SVG code easily enough if you want to get lower values, or I can modify the pens for you.

Let me take a step back here. My current goal is to be able to develop this page in Chrome on this Windows 10 PC. I will be testing on other platforms, but I would like to be able to set colors with some degree of accuracy with this desktop PC. What is my best path forward? If I have been running with a bogus color management profile, then I'll change it, if you can point me in the right direction. I really want to be able to use default browser settings, because I don't expect most users are going to fiddle with chrome flags.

What should I be doing to align myself with whatever the new reality is, and whatever part of the old reality I was mis-rendering?

Deleted: chrome68_red_2.png 25.5 KB

	chrome68_red_2.png 25.5 KB View Download

I realized that I had a printscreen of my page from 06/24, two days before the release of 68. I have made pngs of a small section of that printscreen and a new printscreen with my current 68 + sRGB configuration. That is my clearest demonstration of the change I perceived with the release of 68, even with sRGB as the color profile.

Deleted: blue67.png 28.8 KB

	blue67.png 28.8 KB View Download

Deleted: blue68_sRGP.png 23.0 KB

	blue68_sRGP.png 23.0 KB View Download

My recommendation would be to change the color profile of your monitor to something more standard, like sRGB or (maybe) AdobeRGB (if your monitor has a wide gamut). You can do that in the color management control panel, by choosing Add Profile - both of those options will be present in the default list, I think. Then select it in the short list of profiles on the main dialog, and click 'Set as Default'.

Combined with that, you should double check the monitor setting on the menus (of the actual monitor). These vary by manufacturer, but it may have a choice to set the color mode to sRGB or Adobe, for example. If so, just make sure it's set to match the profile from above.

At that point, you should be getting very accurate color reproduction (and you won't need to override the chrome flags). This is the ideal world going forward, and for most users, your content will look as good as possible. (And any other content you view will also be as accurate as possible)...

I'm taking off for the day, but I'll check back in tomorrow - I still want to discuss that profile you attached with my co-workers, it's fairly unique, even among all the examples we've collected from chrome users...

Thanks for the info. Please let me know what feedback you get from your co-workers.

The only thing I had done re: color profile is in the BenQ menu that pops up when you press a button on the monitor itself. They call it Picture Mode, and I have been using the default "Standard" option, but I just switched to sRGB.  I also changed my Windows profile to sRGB. My monitor is 72% gamut, which is not considered "wide", AFAICT.  Now it's time to get used to the changes...

I'm attaching more expansive pngs as 67 vs 68, in case it matters - easier to see the color or lack thereof.

Deleted: blue67.png 58.1 KB

	blue67.png 58.1 KB View Download

Deleted: blue68_sRGP.png 62.7 KB

	blue68_sRGP.png 62.7 KB View Download

Thanks brianosman@ for your inputs, removing Needs-Bisect as the issue is not reproducible from TE end and is already being investigated by brianosman@.

Thanks...!!

Gentle Ping...

@brianosman: please have a look into it for further triaging this.

Thanks.! 

After discussion, there may be nothing else to do here. We could fuzzily detect profiles like this, but it's still not clear what the right thing to do is. Unlike some of the other bugs, I haven't seen any other instances of this, which tells me this particular type of profile is exceedingly rare.

I am fine now, after setting up my color profiles as sRGB. However I will differ with Brian about the rarity of this configuration. First, I am a developer who was in the middle of finely adjusting colors when this happened, so it was noticeable to me. I would bet that many others are using this same BenQ profile - it's the "Standard" profile for this BenQ Monitor, which is a popular model.

That said, the color differences are relatively subtle, and I don't think this is a big problem for those "many others" who are using this profile.

Re: Comment 13: When I open RL2455.icm using a ICC profile viewer, I see TRC tags with just 5 points each, and a A2B0 tag containing a pure 2.2 gamma curve encoded in 256 points. My impression is that Chrome is supposed to be favoring the A2B0 tag, but the graph you posted looks like a 7-parameter curve fit to the low-resolution TRC. In fact the corner is exactly the same as the first point after black of the low-resolution TRC. What do you think?

Yeah, that's very close to what's happening.

We're fitting the TRC curve to a parametric function, then inverting that to use as a destination profile, where the preferred thing to do is to use B2A0 tags directly.  We've been hesitant to support B2A destinations because we're not confident that we can make them perform well.

Before Chrome 68, we had this very same strategy, but the curve fitting algorithm failed to find a fit to those 5 points and we fell back on a pre-baked sRGB curve.  Post 68 we can now fit those 5 points to an sRGB-like curve with a linear section first and exponential for larger values.  While the linear section fits the two data points it connects perfectly (of course), that linear segment doesn't approximate 2.2 gamma as well as an sRGB curve would.  That there are only 5 points in the curve stretches that first linear segment longer than most.

What's also sort of puzzling is that the profile uses a 5-point TRC curve to approximate a pure 2.2 gamma---presumably to save space?---while there is an even more compact option to express that pure 2.2 gamma exactly as a TRC curve (the N=1 special case).