Issue 6003 - Better handling of no-content-for-platform-message on help.eyeo.com

static/scss/components/_article.scss

 // This file is part of help.eyeo.com.
 // Copyright (C) 2017 Eyeo GmbH
 //
 // help.eyeo.com is free software: you can redistribute it and/or modify
 // it under the terms of the GNU General Public License as published by
 // the Free Software Foundation, either version 3 of the License, or
 // (at your option) any later version.
 //
 // help.eyeo.com is distributed in the hope that it will be useful,
 // but WITHOUT ANY WARRANTY; without even the implied warranty of
@@ skipping 11 matching lines @@
 {
   padding: $md;
 
   @media (min-width: $phablet-breakpoint)
   {
     padding: $lg;
   }
 }
 
 .article-heading,
-.article-browser-selector
+.article-browser-selector,
+#no-content-for-platform-message

[juliandoucette, 2017/11/15 13:27:44]

NIT: Why should this article content have a border-bottom; unlike other article
content?

[ire, 2017/11/15 16:57:30]

I guess I don't really see it as article content. I see it as a separate
message, which is also why I removed it from the .article-body . But as I
mentioned, this is totally a personal suggestion (Jeen didn't ask me to add
this). I just thought it looked better being separated from the rest of the
content.

[juliandoucette, 2017/11/15 18:03:33]

Does it ever not replace the article content as the main content in that area?

[ire, 2017/11/27 18:26:45]

Yes. There are cases where there is "general" content that isn't within a
`.platform-${browser}` container, so that shows even when there is no content
for the specific browser

 {
   padding-bottom: $md;
   margin-bottom: $md;
   border-bottom: 1px dotted $gray;
 }
 
 .article-heading .has-pre-icon
 {
   @media (max-width: $phablet-breakpoint - 1)
   {
@@ skipping 37 matching lines @@
   display: none;
 }
 
 @each $browser in $supported-browsers
 {
   .js .ua-#{$browser} .platform-#{$browser}
   {
     display: block;
   }
 }