Thanks for looking at it. I've continued to work on this problem, so
here is an update, but still Firebug doesn't perform as it needs to to
isolate the point in the CSS where this is being picked up. The
display issue seems to stem from the _a:visited_ element, so those
anchor elements that have been visited, display black font on a black
background. I have tested this even before my post yesterday on at
least 6 browsers as I mentioned. So the strange effect of varying
browser having different displays, was a result of whether each
individual link had been visited or not. You can duplicate with what I
supplied, by visiting on some of those links, and returning to see the
black box replacing the visible link. Look closely at the screen shot
of Firebug, top right and it clearly shows the the color as black, and
the background as white, while the screen shot of the same point,
shows only a black box over that link.
Here's my problem with Firebug: When I select an anchor element that
has been visited, the display is showing that :visited as if it was
not visited a:link {color:#FFFFFF; background-color:#990000;} instead
of as a:visited {color:#000000; background-color:#000000;} for a
visited link, making the tracing and isolation of this coding error
(clearly mine) to show me where in the CSS chain the actual coding
error can be found. If the screen is displaying an element as black on
black, then Firebug should allow show black on black and were each of
the elements has been set to black. That is why I'm posting in this
forum, and not a browser forum somewhere else. The tools are not
showing me what I need to see to find and fix this. I should be able
to quickly see in the chain a pace where these are set to black, and
disable them with the tool in Firebug and have the problem go away - I
just have no such point displayed. If I choose the hover over the
link, the chain does change to reflect the hover condition, but then
it returns to the link condition, and not the visited condition as it
should.I hope I have made this clear, and that something can be
corrected soon.
On Apr 20, 6:28 am, Sebo <[email protected]> wrote:
> I downloaded the two files and checked the display of the links. And
> everything looked normal to me: Links on the page as well as in
> Firebug with black text color and white background. Nav links with
> white text color and maroon background, like shown in Firebug.
> Unfortunately I don't understand some parts of what your explanations.
> You say, Firebug displays the styles as expected, but the page shows
> you the links black on black like in the screenshot?
> Sounds like this is not Firebug related. To test this please create a
> new profile (http://getfirebug.com/wiki/index.php/
> FAQ#Installing_in_a_clean_profile) WITHOUT installing Firebug and load
> your page there. If the problem persists, then you know it's not
> caused by Firebug, but either a bug in Firefox, in another extension
> or in your code. If the problem is gone, install Firebug 1.8.0a1 in
> that new profile and load the page again. If the problem reappears
> afterwards, please create a new issue athttp://code.google.com/p/fbug/issues/
> .
>
> Sebastian
>
> On Apr 20, 9:59 am, JGood4u <[email protected]> wrote:
>
>
>
>
>
>
>
> > The basic problem is that the style and computed traces don't agree with the
> > browser display.
> > I started off yesterday morning making same small changes to the css page to
> > overcome a small display problem in an anchor link - it displayed the wrong
> > background and foreground text color. The entire nav bar change drastically,
> > but should not have.After trying a number of ways to code this, I too the
> > code out of the CSS, and placed it in the HTML page in the heading. The
> > displays got stranger, with some nav bar elements blacked out (black on
> > black) instead of white on red.The originalproblem link also displayed
> > black on black. More strangely, different browser showed different menu item
> > blacked out. All the while, the side bar of FB showed something different
> > from the browser display. What is showed was typically what I wanted, just
> > not what the display showed. I've attached a screen shot of FF4 and
> > FB1.8.0.a1 and the code and webpage causing the trouble. I still need to fix
> > the problem displaying this correctly. but I also need FB to show me where
> > the display is getting its instructions from. The page file I have included
> > is named xevents.php, but is in fact a view of the source as the browser
> > receives it so there is no need to run this through a PHP server. However, I
> > did that to both the web source, and loading that captured file and got
> > different results, but when the 2 files are compared, they are identical as
> > one would expect them to be. But if they are identical, how can they display
> > differently?
>
> > FTP-SV01 2011-04-19 23.48.jpg
> > 123KViewDownload
>
> > FTP-SV02 2011-04-19 23.51.jpg
> > 54KViewDownload
>
> > main.css
> > 3KViewDownload
>
> > xevents.php
> > 3KViewDownload
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
