Resizing font size of modules

[MMRIZE]

@Rags
custom.css should be placed in your ~/MagicMirror/css, where the custom.css.sample exists still or had existed once.

[Rags]

@MMRIZE It is still placed there ( /home/pi/MagicMirror/css/custom.css) , and configured with font-size:60px. I only copied that file into newsfeed module folder since the font size was not increasing, and thought to just try if it works by placing it into the newsfeed module folder.

[MMRIZE]

@Rags

Try this in your custom.css

.newsfeed-title {
  font-size: 60px;
  color: green;
}

.newsfeed-source {
  font-size: 40px;
  color: magenta;
}

[sdetweil]

@MMRIZE you should follow the correct model

.modulename ....... {

}

while it didn’t make acdifference here, it will sometime

[sdetweil]

@Rags in the case where there is no space between the class names

.xxx.yyy

that means they are ALL specified together on the same element

when there IS. space
.xxx. .yyy

that means the element which is a child of the element with the more left

.xxx
.yyy

iframe however is hard, cause you don’t have control of what is inside the iframe, it has its own document and css tree

again the developers window will help

if things are selected I. the custom.css u provide that means I spelled it wrong or the order is wrong…
oh and css is case sensitive just like JavaScript

[Rags]

@MMRIZE I am stumped. The changes to the color happened, but the resizing still not responding.

[sdetweil]

@Rags while in the developers window, with the element u want to change selected , the upper right window in the dev env allows you to apply styles to that element. (green box)

so color, font-size, etc…
in the middle pane pof the dev env, on the bottom row is the selector path to that element (pink box)

[MMRIZE]

@Rags
C of ‘CSS’ is cascading.
Probably somewhere in your css files, the prior selector of the same target would be defined with font-size.

You can watch which selectors and properties are linked to your target element with the frontend dev-console.

Or you can just restart with “clean” custom.css again and just add one rule and check how it works. Then do one-by-one until you can understand what you are doing now.

Good luck.

[Rags]

@sdetweil
Obviously i am doing something wrong.
I am unable to get to the style even when newsfeed element is highlighted. Or, the style is picking up from main.css and changing anything here will impact all styles.

[sdetweil]

@Rags you are in the script section, not the body , click body, bottom left
use the arrow top right to select the part of the MM screen (it will highlight as u move over it)

[Rags]

@sdetweil

[sdetweil]

@Rags expand the module_content element

u are not selecting the title to view

set the module refresh time to 60 seconds (updateInterval:60000) in config.js while you fiddle with the css

I added a custom.css entry

.newsfeed .newsfeed-title {
   font-size: 30px;
}

you can see it was used here
and the style medium (strikethru) has been overridden by something with font-size higher up.

[Rags]

@sdetweil i am sorry but i am unable to follow correctly what u are advising. However, the HTML code does not seem to contain the newsfeed title descrp.
i think i selected the module content to expand, and i also changed the custom.css entry as suggested. The style display window is not showing the newsfeed entry. I am again not sure if i am doing the right thing. Anyways i am learning as we go.
On second thoughts the process of changing the font size is so tedious (as it seems to me now), I wonder if there is an alternate way.

[sdetweil]

@Rags but you didn’t select the actual content (note that it is replaced every updateInterval time cycle… )

if u aren’t looking at the actual element, then you won’t see its classes and styles…

sometimes this is tedious work.

here is an updated image with the areas selected in white,
highlighted content (left screen)
expanded document w selected content (middle)
class tree (right)

and I used the mouse pointer (pink) to allow highlight and click on the newsfeed title

and you can test type the styles in the top box, (green) , to make sure they are right, before you copy/paste that section to the custom.css

[Rags]

@sdetweil
After struggling, this is what i managed to take a screenshot of. It does not show the styles of the selected content in the dev screen.

[MMRIZE]

@Rags
It means your CSS(probably custom.css) is not applied.

The reasons might be;

• Fail to load custom.css (invalid file name or location)
• Syntax error in your custom.css

I can see the red circled X mark in your console. You can check it in Console tab(right of Elements tab) or click that mark directly.

[MMRIZE]

@Rags

To make things simple;

1. All other modules except newsfeed, remove or disable them. (It seems you have more than 28 modules currently)

{
  disabled: true, // <-- toggle the module disabled/enabled
  module: "weather",
  position: "top_right",
  ...

2. Return to custom.css to the original, or remove all its contents.

3. Now, I’ll assume you have a clean CSS.

4. Then just add this into your custom.css and save it.

.newsfeed .newsfeed-title {
  font-size: 60px;
}

.newsfeed .newsfeed-source {
  font-size: 40px;
}

5. Let’s see what happens when MM runs.

[sdetweil]

@Rags using your image, marked up for color

the styles tree pane (right side, orange) shows info for only ONE element at a time

look at the bottom row of the element tree pane(left side, blue), right edge, says u have the module-content element selected (purple), not the newsfeed-title element(green)

because the module replaces it’s content every updateInterval cycle, the developers window will reselect the first element not replaced if your selected element disappears

that’s why I said set the interval to 60 seconds to give u time to look and change

[Rags]

@MMRIZE Finally ! Finally…
I disabled all modules, except newsfeed, then cleared out the custom.css configs and added a fresh config for newsfeed as suggested above and finally it worked.
So was the issue just because of the corrupt custom.css?
Anyways, this issue has enabled me to learn working with the developer console. I am glad.
Thank you @MMRIZE and thank you @sdetweil . Ever obliged.

[sdetweil]

@Rags glad u got it working

one thing to note, if there is a syntax error in the custom.css, everything ABOVE the error will work, everything AFTER will not