Mailinglist Archive: opensuse-web (19 mails)

< Previous Next >
Re: [opensuse-web] Again broken wiki CSS
Hello,

@Matthew: can you please check if there's something wrong with the
server?

http://en.opensuse.org/load.php?debug=false&lang=en&modules=mediawiki.legacy.commonPrint%2Cshared&only=styles&skin=bentofluid&*
is delivered gzip-compressed - but it seems the HTTP response header
does not state that.

The result is that Firefox only sees binary crap (gzip'ed CSS) instead
of the content of MediaWiki:Common.css :-(
(Funnily Konqueror (webkit mode) seems to auto-detect the encoding and
can use the CSS delivered via load.php.)

Note: Testing with "telnet en.opensuse.org 80" without "Accept-Encoding
gzip, deflate" is pointless for obvious reasons ;-)



(sorry for replying to the "wrong" mail - KMail ate your second one :-/

Am Dienstag, 17. Juli 2012 schrieb Rajko:
Templates lost some elements,. box-footer lost bottom part.

That's no reason to revert the (unrelated) @media print changes ;-)

The real fix is:

diff --git a/bento/css/base.fluid.fix.css b/bento/css/base.fluid.fix.css
index 4316794..56c20e3 100644
--- a/bento/css/base.fluid.fix.css
+++ b/bento/css/base.fluid.fix.css
@@ -5,5 +5,6 @@
/* left: 0;*/
/* margin-bottom: 0!important;*/
position: relative;
- margin-bottom: -15px!important;
-}
\ No newline at end of file
+ margin-bottom: -10px!important;
+ margin-top:0;
+}

BUT that's something we already have in MediaWiki:Common.css.

@Rajko:
My CSS testbed is always Firebug or the Web Developer Toolbar, and I
only do changes to Mediawiki:Common.css after testing them locally.
In other words: the risk that I break something is very low ;-)

Nevertheless, can you please give me admin permissions on languages.o.o?


Regards,

Christian Boltz
--
Das soll jetzt wirklich keine Arroganz sein, aber es macht keinen Sinn,
das Haus abzureissen, weil du den Hausschl├╝ssel vergessen hast. :-)
[Ratti in suse-linux]

--
To unsubscribe, e-mail: opensuse-web+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-web+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References