I was wondering why the default background color of the header in child-theme thegem-child differs from the background color in child theme thegem-child-user-icons. Both these child themes load an extra css file called custom.css (in the /css dir).

The gem child says (from line 1157) :
#site-header,
#site-header-wrapper,
.header-layout-fullwidth_hamburger #primary-menu {
            background-color: #212331;
}

#site-header.fixed.shrink {
            background-color: rgba(33, 35, 49, 0.95);
}

The gem child user icons says (from line 1166):
#site-header,
#site-header-wrapper,
.header-layout-fullwidth_hamburger #primary-menu {
            background-color: #ffffff;
}
#site-header.fixed.shrink {
            background-color: rgba(255, 255, 255, 0.95);
}
#site-header.fixed.shrink.fill {
            background-color: rgba(255, 255, 255, 1);
}

Personally I think that the white background color should also be default in the thegem-child theme, because the default logo (not the white one) isn’t really visible on top of the dark background.

I can fix this, but I help others install this theme and it’s hard to tell them to change the custom css first.

I hope to hear from you soon.

Best, Lauren

I've attached a few screenshots which indicate that there's a /css/custom.css file included in the child-themes. The child themes I refer to are extracted from a zip file archive provided via Themeforest (themeforest-16061685-thegem-creative-multipurpose-highperformance-wordpress-theme.zip).

As you can see a dark #site-header appears when I install the default child theme of thegem (on a somewhat new Wordpress installation, I've just added one extra plug-in). As i stated in my first ticket, I've noticed that the custom.css file in child theme "Thegem-child-user-icons" differs from the custom.css file in "Thegem-child".

I will send you credentials for our site in a private message.

You're right, I've noticed the comments in the custom.css file. After saving the theme options (without editing anyting) the header turned white. It might be a bit confusing that this step is needed in order to give the site a default setup after installing the default child theme. But it works! 

Thanks for your quick responses.