Last modified: 2004-08-17 16:38:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 86 - User style editing preview not correct in Camino
User style editing preview not correct in Camino
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: 99 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2004-08-16 06:00 UTC by Timwi
Modified: 2004-08-17 16:38 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Timwi 2004-08-16 06:00:05 UTC
Originally submitted by kelvSYC (kelvsyc)  2004-07-14 08:30

In Camino 0.8 for OSX 10.3.4, I discovered a really
weird bug while editing my monobook.css file.

I go to the edit page, and press preview without
actually changing anything, and the rendering is all of
a sudden different (in the sense that before, some of
my rules overrided those provided by MediaWiki, while
after, those rules were being overridden by those
provided by MediaWiki).  I haven't tried what would
happen if I saved this "change" (even though I did not
change anything).

The only significant changes in the source is the

Before clicking preview:
    <style type="text/css">/*<![CDATA[*/ @import

After clicking preview:
    <style type="text/css">/*<![CDATA[*/ @import
a {
text-decoration: underline;
color: #0000FF !important;

/* CSS2.1 uses one colon for pseudo-classes, while the
proposed namespace-aware CSS3 uses two (to distinguish
it from an element inside another namespace).  So that
it is both backwards and forwards compatible, I have
both here. */
a::visited { color: #7F007F !important; }
a::active { color: #FF0000 !important; }
a:visited { color: #7F007F !important; }
a:active { color: #FF0000 !important; } { color: #FF0000 !important; }
a.interwiki, a.external { color: #3366BB !important; }
a.stub { color: #772233 !important; }

#bodyContent ul > li, #p-nav ul > li, #p-tb ul > li,
#p-lang ul > li {
list-style-image: none;
line-height: normal !important;

#p-tb, #p-nav, #p-lang, #p-personal, #p-logo {

#p-search {
width: 100%;
left: 0;
top: 0;
z-index: 0;
#p-search h5 { display: none; }
#p-search .pBody { background: none; text-align:right;
border: none; }

#p-cactions { font-size: 100%; }
#p-cactions ul { margin: 0; }

#p-cactions li.selected { font-weight: bold; }
#p-cactions li a { text-transform: none; }
#p-cactions li { padding: 1px; }

/* hack until bug is fixed */
#p-cactions a { color: #FF0000 !important; }

#p-personal { top: 155px; }
#p-nav { top: 235px; }
#p-tb { top: 340px; }
#p-lang { top: 410px; }

#p-lang .pBody { height: 185px; overflow: auto; }

#p-personal .pBody {
    margin: 0;
    background: White;
    border: 1px solid #aaaaaa;
    padding: 0 0.8em 0.3em 0.5em;

#p-personal ul {
    list-style-type: square;
    margin: 0.3em 0 0 1.5em;
    text-transform: none;

#p-personal li {
    display: list-item;
    margin: 0 0 0 0;

#p-personal a {
text-decoration:underline !important;

li#pt-userpage { background: none }

#footer {
    float: right;

#globalWrapper { font-size:100%; }

h1, h2, h3, h4, h5, h6 {
font-family: "Bitstream Vera Sans", "Lucida Grande",
Verdana, Lucida, Helvetica, Arial, sans-serif;

#bodyContent * {
line-height:normal !important;

body {
font: x-small "Bitstream Vera Sans", Verdana, "Lucida
Grande", Lucida, Helvetica, Arial, sans-serif;
background-attachment: fixed;

Screenshots can be provided on request.


------------------------- Additional comments ------------------------
Date: 2004-07-29 08:04
Sender: SF user vibber

Can you please narrow this down to a minimal case, test in another
browser, and provide screenshots?

Also be sure that you've got the current styles loaded; there
are awful
horrid cache issues with this stuff.
Comment 1 Rowan Collins [IMSoP] 2004-08-16 23:27:34 UTC
*** Bug 99 has been marked as a duplicate of this bug. ***
Comment 2 Timwi 2004-08-17 16:37:49 UTC
The error was this:
    <style type="text/css">/*<![CDATA[*/ @import

Notice:   @import " ... );

I already fixed this a few months ago.

Adding brion to CC list because he replied to the SourceForge instance of this bug.
Comment 3 Timwi 2004-08-17 16:38:15 UTC
I meant a few *weeks* ago. :)

Note You need to log in before you can comment on or make changes to this bug.