If we're going to let this pass as a "feature, not a bug", then the Quick Save label should say "Bake (Combined)", or "Bake (Normal)" according to which baking pass the button stored when saved. If it shows just "Bake" as it does, it's a bug, given that you're suppose to be just quick-saving the "Bake" button alone, and that should bake whatever it's selected for its pass at the given moment.
Jan 16 2020
Jan 8 2020
Dec 27 2019
May 15 2019
@Joaquín Kierbel (Jk), the use of sRGB does not affect the range of values that can be represented, it is 0..1 regardless.
It's not useful to discuss implementation details except with developers who understand the code. Just tell me loading 8bit S-Log textures or whatever is actually something people do, and then we can figure out a solution and give fixing that some priority.
The use of sRGB EOTF only affects how the quantization is distributed, the colorspace conversion from the specified colorspace to scene linear still happens.
May 14 2019
Feb 13 2019
Actually, those color boxes only look different in regards to what it's selected in the "Display device" setting, not the view-transform, which causes no changes on the appearance of the color box.
So in the only sense that those boxes are "managed" is that they are tied to the "sRGB" field in the Display Device setting, but nothing else.
So yes, if you change that setting to any other option available (like None in the captures from this report) they look something else instead of sRGB-like, but that is it. View-transform isn't in the chain there, regrettably. All color related fields in Blender's UI should at least have a checkbox to go through the pipe of all transforms in the color-management panel.