SitePoint Sponsor

User Tag List

Results 1 to 8 of 8
  1. #1
    Team SitePoint AlexW's Avatar
    Join Date
    Apr 2000
    Location
    Melbourne
    Posts
    832
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)

    Glitch : Netscape 6 (6.1-6.2) and visited links

    Riddle me this!

    You may have noticed recently that SitePoint has changed our CSS. Mainly usability tuning.

    One of the key changes was to make visited links appear
    a dull purple to give you instant recognition of links you've already visited. An oldy but a goody.

    This is fine in IE, but Netscape 6 (which I normally quite like) is being weird with visted links.

    For example:
    The links from the front page to the forum threads (class="latestTopicLink") turn purple after you've been there, like so.

    Code:
    .latestTopicLink{
    	font-weight: bold;
    	font-family:Verdana, Arial, Helvetica, sans-serif;
    	font-size: 12px;
    	color:#0022AA;
    	line-height: 15px;
    }
    a:hover.latestTopicLink {
    	color:#3a77EE;
    }
    a:visited.latestTopicLink {
    	color:#663366;
    }
    But the article links above them, applied in the same fashion, stay blue regardless of your visitation.

    Code:
     
    .featureTitleLink {
    	font-weight: bold;
    	font-family: Arial, Helvetica, sans-serif;
    	font-size: larger;
    	color:#0022AA;
    	line-height : 120%;
    	text-decoration: underline;
    }
    
    a:hover.featureTitleLink {
    	color: #3a77EE;
    }
    a:visited.featureTitleLink {
    	color: #663366;
    }
    But even stranger, the 'hover', applied in identical fashion, works fine.

    I read somewhere that NS6 has a bug that means visited links only work when they are link outside the domain they are in.

    Fair enough, but all these front page links link outside their domain (to sitepointforums.com, webmasterbase.com, etc) so that's not the answer.

    View the stylesheet here (yes it's a PHP file - it's an interactive CSS doc that detects browsers and adjusts itself)

    Any ideas?
    Alex Walker
    SitePoint Developer
    SitePoint - Learnable

  2. #2
    We like music. weirdbeardmt's Avatar
    Join Date
    May 2001
    Location
    Channel Islands Girth: Footlong
    Posts
    5,882
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Completely off the top of my head, so I may well be wrong, but are you sure NS6 supports "larger" as a font-size attribute? I have had experiences with NS where if you put one thing it doesn't like, it ignores the rest of that class.

    Like I said, totally off the top of my head...
    I swear to drunk I'm not God.
    » Matt's debating is not a crime «
    Hint: Don't buy a stupid dwarf ö Clicky

  3. #3
    Team SitePoint AlexW's Avatar
    Join Date
    Apr 2000
    Location
    Melbourne
    Posts
    832
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    It's a reasonable guess. We choose to use 'larger/smaller/medium' rather than pixels measurements for some of our key styles so IE would scale it with it's View/Text Size.

    But the 'sitemap-style' menu at the bottom still uses pixel measurements and still won't seem to turn purple when asked to. So does the side nav.

    And it still renders the hover, so it's not like it just stops and gives up.

    So I don't think that's it.

    Very strange.
    Alex Walker
    SitePoint Developer
    SitePoint - Learnable

  4. #4
    SitePoint Addict
    Join Date
    Jul 2001
    Posts
    284
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I got a bit confused reading all of that, but then again, coffee hasn't kicked in yet...

    Anyways... I generally put by hover parts after the visited parts. It was a bug I found out and that seemed to fix things.

    Sorry if that was totally off the topic at hand, but oh well.

  5. #5
    Team SitePoint AlexW's Avatar
    Join Date
    Apr 2000
    Location
    Melbourne
    Posts
    832
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    htmlite, I think you understand the problem right.

    I tried your fix and got some interesting results.

    From my tests, it has seemed to have fixed it on the EcommerceBase/WebmasterBase/etc side navigation, but not anywhere else (referencing the same CSS).

    It has also activated the hover on the visited links that *do* work (like the Latest Discussion Forum link). Before the hover was dead if you had visited the link beforehand (which I didn't mind, actually)

    It's hard to pick a pattern here
    Alex Walker
    SitePoint Developer
    SitePoint - Learnable

  6. #6
    Team SitePoint AlexW's Avatar
    Join Date
    Apr 2000
    Location
    Melbourne
    Posts
    832
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    I just ran it through the W3C validator and it came up fine.

    SitePoint stylesheet
    Alex Walker
    SitePoint Developer
    SitePoint - Learnable

  7. #7
    SitePoint Addict
    Join Date
    Jul 2001
    Posts
    284
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    You have an extra css set that may be mixing things up...
    Code:
    a:visited.navbody {
    	color:#663366;
    }
    a:hover.navbody {
    	color:#3a77EE;
    }
    a:visited.navbody {
    	color:#663366;
    }
    Take out the last one there and see how that goes.

  8. #8
    SitePoint Wizard
    Join Date
    Jan 2001
    Location
    Milton Keynes, UK
    Posts
    1,011
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    On line 130 you've got yet another a:visited.navbody.

    Also, the order of the pseudo classes is important.

    Example(s):
    A:link { color: red } /* unvisited links */
    A:visited { color: blue } /* visited links */
    A:hover { color: yellow } /* user hovers */
    A:active { color: lime } /* active links */

    Note that the A:hover must be placed after the A:link and A:visited rules, since otherwise the cascading rules will hide the ’color’ property of the A:hover rule. Similarly, because A:active is placed after A:hover, the active color (lime) will apply when the user both activates and hovers over the A element.
    If this helps Alex, could I ask a favour of the Sitepoint team? Could you use add an id for the <textarea> element used for posts? The reason I ask is so that I can use my own stylesheet to modify the size of the <textarea>.

    Bit of a cheek but no harm in asking.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •