Read the statement by Michael Teeuw here.
Calendar Doesn't Honor custom.css for Background
-
@ember1205 like this custom.css
body { } .currentweather { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; } .weatherforecast { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; } .clock { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; }
you don’t do
.module.clock
-
@ember1205 and to change the color of the DATE of the digital clock (which uses the date class)
.clock .date { color: green; }
-
Ok. I will look into making those changes and see if I can get it working the way that I want.
Why does “module.currentweather” work fine, though (along with the others that I mentioned)? CSS has always been a weak spot for me…
-
@ember1205 said in Calendar Doesn't Honor custom.css for Background:
Why does “module.currentweather” work fine
no idea… css is my weakest skill
-
Calendar still does not pick up any CSS controls from the main custom.css file. Here is a snippet of what I added:
.calendar { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; }
I modified the other sections to look like this:
.module.clock { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; } .module.currentweather { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; } .module.weatherforecast { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; }
They work fine “either way”. Calendar refuses to pick up the formatting from the custom.css file it seems and I have to put the controls into the calendar.css file in the module’s directory.
-
@ember1205 hm… custom.css should override everything… it is loaded last
-
hm…
.calendar .title { color: blue; }
works for me
from the readme| `titleClass` | Add a class to the title's cell. | `timeClass` | Add a class to the time's cell.
one not documented is the ‘symbolClass’
-
@ember1205 part of the other problem is calendar doesn’t have a cohesive background element… it has table rows of elements…
but there is a tableClass setting, which you can use in config.js to force a particular class
but you HAVE to do this, else no special class is applied -
I found and fixed it (sort of). I had added content to my custom.css file to create a blurred background image as I was experimenting with some display options. I commented that content out (or so I thought) and placed all of these controls “after” that section in the custom.css file.
Through a variety of changes that I was making to try and track this down, I noticed through viewing the Developer options with a real browser and looking at the elements that whatever section came first after my blurred background section wasn’t being picked up. As I rolled the changes down to the bottom, I was seeing different sections stop working.
Seems to be all fixed now, and is clearly not a bug in the product but was a bug in my custom.css content. After deleting the content, all is displaying properly.
-
@ember1205 so, this custom.css works
body { } .clock .date { color: green; } .calendar .title { color : blue; } .calendar .fribble { background-color:rgba(32,32,32,0.6); border-radius:8px; padding:8px; }
with
module: "calendar", config: { tableClass:"fribble" }