On Monday, May 8, 2017 at 5:42:04 AM UTC-4, Mauro De Lauretis wrote:
>
> absolutely nobody can help me?
>>
>>
>>
the forecast table should not be or inherit a 100% width.

your most effective tool for debugging these things would be to use any 
modern web browser to look at the DOM tree of your web pages.  turn on/off 
various CSS attributes until you figure out what is causing the layout that 
you do not like.

from a cursory glance at the html, you have a double 'forecast' div (two 
'div' elements, both of which have class 'forecast').  while not 
necessarily a problem in itself, that kind of sloppiness often leads to 
layout problems.

the column alignment you specifically note is due to interactions between 
the CSS in forecast.css and the CSS in the niculskin (or derivative) report 
template that you are using.  the niculskin CSS forces every table to be 
100% width, and that messes up the layout of the forecast table.

card table {
    width: 100%;
}

you could override it with something like this:

forecast.forecast table {
    width: 100px;
}

(the forecast.forecast is because of the sloppy DOM hierarchy you have)

the CSS/html developer tools in firefox/chrome/ie will help you get it 
right.  for example, in firefox do tools -> web developer -> inspector

m

 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to