The status of any given module on the "Available updates" page @ admin/logs/updates appears on the line above the title of the module.

See attached image.

NB: Disregard the missing padding on the table cells in the attached image. That is due to basic CSS reset of HTML default layout.

Examining the generated HTML and the "update_status.css" file revealed that the class "version-status" is undefined.

Also the status icon could use a little air on the left side.

I propose adding these two rules to the "update_status.css" file:

.update-status .version-status{
  float: right;
}

.update-status .icon {
  margin-left: .5em;
}

On a side note ... the following two rules are currently not in use.

.update-status .top-row {
  border-top:2px solid black;
}

.update-status .bottom-row {
  border-bottom:2px solid black;
}
CommentFileSizeAuthor
#3 update_status.css_.patch.txt245 bytesTiburón
#1 update_status_missing_css_fix.png6.21 KBTiburón
update_status_missing_css_bug.png6.73 KBTiburón

Comments

Tiburón’s picture

Tiburón commented
StatusFileSize
new update_status_missing_css_fix.png6.21 KB

Here is an image showing the effect of adding the two CSS rules...

Tiburón’s picture

Tiburón commented

Hold your horses .... something else is at foot ... Firebug tricked me and only showed me a subset of the rules in the CSS file. Well I should have done a manual check also :-(.

I will dig further to find the reason to why the existing rules are not applied.

Tiburón’s picture

Tiburón commented
Status: Active » Needs review
StatusFileSize
new update_status.css_.patch.txt245 bytes

Removing all other stylesheets except "update_status.css" did not help so I investigated the possibility of encoding problems (think phishing URLs).

That was also a dead end but I noticed that all rules had two linefeeds between them except the two targeting "version-status".

Well I added a linefeed and it worked.

Patch attached.

merlinofchaos’s picture

merlinofchaos commented

A linefeed?

Browsers are crazy. This issue should be bronzed as a shining example that browsers are crazy.

dww’s picture

dww
we/he/they
commented

isn't this going to get aggregated and compressed and *all* the linefeeds stripped out of it by the core .css optimizer functionality? i thought .css was whitespace-insensitive. wtf? ;)

btw, which crazy browser is it?

Tiburón’s picture

Tiburón commented

I would think so too. Before adding the linefeed I ran it through W3Cs validator and it didn't find anything wrong.

But Firefox 2.0.0.4 on Windows XP for some reason think that linefeed is important. I don't have other versions of Firefox installed to test so...

dww’s picture

dww
we/he/they
commented
Status: Needs review » Fixed

I'm guessing that browser will be horribly broken and confused by the css compressor in core, but that's not my problem. ;) The change makes update_status.css more consistently formatted, anyway, so why not? Committed to HEAD.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)