Forum Moderators: not2easy
<style type="text/css">
#alice-wrapper {
margin: 1em 2em 10em 2em;
}
p {
font-size: 1.1em; line-height: 1.6em;
}
p.asterisks {
font-size: 150%; font-family: monospace; text-align: center;
}
</style>
I am drawing from an external stylesheet to call the page background:
.bg-b {
background: #fff4e1 url(../images/backgrounds/white-brown-108.jpg);
}
<body class="bg-b">
.......................
It tested fine. It was posted live and tested fine. FF, Opera, IE. Went back today to take another look at the page (FF) and the page flashes for a moment and then is simply black. The only 'color' on the page are the <hr /> and intermittent splotches of the background image at the top, right side (an inch high), and the bottom (couple of inches) - but not consistently. If I 'slam' the scroll bar to the bottom of the page, the last four or five paragraphs will display, and the background is fine - for about 8 inches. Even touch the page and, zap, all black again.
IE - still perfect. Opera - still perfect. FF on my machines here - perfect. Only live on FF is the background color and image gone - and a black background-color: is coming from ? where? I don't use black backgrounds or colors anywhere on the external stylesheet. #000 only appears on some borders - none of which are called for this page.
It's the full text, so about 160kb, but so what? I did go through the entire text and take out all of the old - align="center" - and such (plugging in my global declarations from the external stylesheet - .center {text-align: center;} and the page validates XHTML Strict. CSS validates with one error and three warnings, none of which apply in way to this page- or should matter anyway.
The thing is, this page tested perfectly when it was posted live. Wha' happened? Only live on FF is there an issue - and it wasn't there before. Nothings has changed? I can't test the problem when it works perfectly here. Am totally lost as to where the black is coming from.
BTW - I can 'highlight' the text and it is right there, but black text on a black background doesn't look too good.
I've viewed the 'live' source and CSS in FF and all is as it should be.
I'm baffled, and don't really have any information to provide. Is there a 'precedent'?
Shift reload and/or clear the cache ? You might have an intermittent collection?
What version of Firefox are you using? Any add-ons that might be changing the content ?
I used the Web Developer extension to toggle every conceivable configuration of disabling styles. Results were NOT 100% consistent, there was variance in rendering, but the bottom line was that any background MIGHT last for a view or two, but would be overridden and I would get a black page.
I tried moving the background call from the external sheet and embedded it in the etext. No go.
Again - it works perfectly on machines here. Only live does this show up - so I've had to upload every tweak to get a look at what a user will actually see? I don't get this?
I found a support.mozilla.com bug reference [support.mozilla.com] which notes a potential problem with forced white or black backgrounds in FF 3.5 with files above 250kb. As previously noted, this etext comes in at about 160kb. However, the problem described is extremely similar what is happening with my page.
I broke out the first two chapters into individual pages. They work perfectly live. There does indeed seem to be a bug in FF CSS in large files. The size that triggers the bug seems unclear. Though large, my page is much smaller than the reported page.
Is anyone aware of this bug and its status? Is it something that will be corrected? Could an add-on be related? That seems unlikely as every other page on this website renders perfectly. This is the only exceptionally large page.
I've got a slew of add-ons, but nothing that should be the source of causing the issue from here?
I may have to break this page down into chapters and link to each of the twelve chapters as individual pages. Not such a bad thing actually. On the access page; besides the link to the page itself, I did add links to jump to each chapter, and that was/is sufficient, but may not be workable. Probably faster just to bust the book down to chapters and be done with it.
