Comments on: Suggestion for new link pseudo-class, “:current” http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/ and other random particles... Fri, 27 Apr 2012 00:00:56 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Kotek http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-1724 Kotek Sat, 14 May 2011 23:11:24 +0000 #comment-1724 I love this idea. I have had the same idea and to be honest I am really surprised that there isn't :current pseudo-class I love this idea. I have had the same idea and to be honest I am really surprised that there isn’t :current pseudo-class

]]> By: Daniel Luz http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-929 Daniel Luz Mon, 30 Jul 2007 21:34:57 +0000 #comment-929 Ian Thomas got it straight to the point: unfortunately, it's not really that simple to tell what links effectively point to the current website (and he didn't even mention anchors). Ian Thomas got it straight to the point: unfortunately, it’s not really that simple to tell what links effectively point to the current website (and he didn’t even mention anchors).

]]> By: Ian Thomas http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-926 Ian Thomas Mon, 30 Jul 2007 15:45:47 +0000 #comment-926 Nice idea, but you'd run into difficulties identifying the "current" page on any but the simplest sites.<br /> <br /> How would you avoid the problem of get/post variables? For index.php?referrer=abc you would probably want to match on index.php, but for page.php?id=123 the id parameter is important. Then of course you've got index.php?id=123&referrer=abc ;)<br /> <br /> Also, what about domains and sub-domains? Are <a href="http://www.mydomain.com/index.html" rel="nofollow">http://www.mydomain.com/ind...</a> and <a href="http://mydomain.com/index.html" rel="nofollow">http://mydomain.com/index.html</a> the same page? What about <a href="http://www.mydomain.co.uk/index.html?" rel="nofollow">http://www.mydomain.co.uk/i...</a> Or <a href="http://www.mydomain.com/?" rel="nofollow">http://www.mydomain.com/?</a><br /> <br /> Maybe some form or regular expression, but then you're getting to the point where its probably easier just to use server-side scripting. Nice idea, but you’d run into difficulties identifying the "current" page on any but the simplest sites.

How would you avoid the problem of get/post variables? For index.php?referrer=abc you would probably want to match on index.php, but for page.php?id=123 the id parameter is important. Then of course you’ve got index.php?id=123&referrer=abc ;)

Also, what about domains and sub-domains? Are http://www.mydomain.com/ind… and http://mydomain.com/index.html the same page? What about http://www.mydomain.co.uk/i… Or http://www.mydomain.com/?

Maybe some form or regular expression, but then you’re getting to the point where its probably easier just to use server-side scripting.

]]> By: Jesse Ruderman http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-925 Jesse Ruderman Mon, 30 Jul 2007 11:56:35 +0000 #comment-925 I agree with Raf; I'd rather continue to discourage page authors from making pages link to themselves. See <a href="http://www.useit.com/alertbox/20031110.html" rel="nofollow">http://www.useit.com/alertb...</a> #10 for some additional reasons that avoiding self-links is good usability practice.<br /> <br /> That said, I don't agree with some of the objections mentioned here:<br /> <br /> Gandalf, this feature would not introduce a privacy issue, because it would only apply to the URL loaded in the current tab.<br /> <br /> Ami, your problem with this feature can be solved by using display:block links :) They're easier to click, too. I agree with Raf; I’d rather continue to discourage page authors from making pages link to themselves. See http://www.useit.com/alertb… #10 for some additional reasons that avoiding self-links is good usability practice.

That said, I don’t agree with some of the objections mentioned here:

Gandalf, this feature would not introduce a privacy issue, because it would only apply to the URL loaded in the current tab.

Ami, your problem with this feature can be solved by using display:block links :) They’re easier to click, too.

]]> By: Raf http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-924 Raf Mon, 30 Jul 2007 11:06:04 +0000 #comment-924 I have mixed feelings about this.<br /> <br /> Pro: there is certainly demand for something like this. Indeed, more than once have I seen people complaining that the :active pseudoclass does not do what they expected ('selecting' the current page), so it's probably not too far-fetched.<br /> <br /> Con: one of the advantages of server-side scripting is that it easily allows you to make sure the menu entry for the current page *is not even a link*. Thus, the current page can easily be distinguished, even when CSS is not applied (keep in mind that CSS is designed to be optional). Plus, I always get confused when a page links to itself - or maybe that's just me :-) I have mixed feelings about this.

Pro: there is certainly demand for something like this. Indeed, more than once have I seen people complaining that the :active pseudoclass does not do what they expected (‘selecting’ the current page), so it’s probably not too far-fetched.

Con: one of the advantages of server-side scripting is that it easily allows you to make sure the menu entry for the current page *is not even a link*. Thus, the current page can easily be distinguished, even when CSS is not applied (keep in mind that CSS is designed to be optional). Plus, I always get confused when a page links to itself – or maybe that’s just me :-)

]]> By: gandalf http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-923 gandalf Mon, 30 Jul 2007 09:52:53 +0000 #comment-923 how does it play with the risk of security issues? My initial thought is - hey! so easy to bruteforce check what websites you have open in other tabs/windows... how does it play with the risk of security issues? My initial thought is – hey! so easy to bruteforce check what websites you have open in other tabs/windows…

]]> By: Fred http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-922 Fred Mon, 30 Jul 2007 08:57:18 +0000 #comment-922 So, I see a problem here that just having this pseudo-class won't get it implemented anywhere. And if (particularly!) MSIE users can't see what you coded, most designers will fall back to server-side scripting again to make it show up for theses users as well. And the overhead of doing it in two places will probably (and sadly) prevent adoption of it.<br /> <br /> On another side note, please don't publish your commenters' email addresses, in particular not in plain text in the source of the page, 'cause that's an invitation for spammers to harvest them. So, I see a problem here that just having this pseudo-class won’t get it implemented anywhere. And if (particularly!) MSIE users can’t see what you coded, most designers will fall back to server-side scripting again to make it show up for theses users as well. And the overhead of doing it in two places will probably (and sadly) prevent adoption of it.

On another side note, please don’t publish your commenters’ email addresses, in particular not in plain text in the source of the page, ’cause that’s an invitation for spammers to harvest them.

]]> By: Ami Ganguli http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-921 Ami Ganguli Mon, 30 Jul 2007 02:23:47 +0000 #comment-921 Sounds like a great idea, except...<br /> <br /> You would need to have some way to apply a the style to a surrounding block as well. If you could associate a url with arbitrary html elements then it might work.<br /> <br /> Then you could add an href element to a div, for example, which would have no effect except that it could be used to determine the CSS style. Sounds like a great idea, except…

You would need to have some way to apply a the style to a surrounding block as well. If you could associate a url with arbitrary html elements then it might work.

Then you could add an href element to a div, for example, which would have no effect except that it could be used to determine the CSS style.

]]> By: Grey http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-920 Grey Mon, 30 Jul 2007 02:15:33 +0000 #comment-920 Yes, I just now got the "please confirm" for archiving message, so it should go out the the membership soonish.<br /> <br /> Also, I'd love to see that URL, but it requires authentication. :)<br /> <br /> 1998, eh? Sounds encouraging... Yes, I just now got the "please confirm" for archiving message, so it should go out the the membership soonish.

Also, I’d love to see that URL, but it requires authentication. :)

1998, eh? Sounds encouraging…

]]> By: Daniel Glazman http://burntelectrons.org/2007/07/suggestion-for-new-link-pseudo-class-current/comment-page-1/#comment-919 Daniel Glazman Mon, 30 Jul 2007 02:13:13 +0000 #comment-919 I never received your msg from the mailing-list. Are you sure you correctly subscribed ?<br /> <br /> Anyway, please see this URL : <a href="http://www.w3.org/Style/Group/WD-CSS-future#id16717669191" rel="nofollow">http://www.w3.org/Style/Gro...</a><br /> <br /> I suggested that back in 1998... I never received your msg from the mailing-list. Are you sure you correctly subscribed ?

Anyway, please see this URL : http://www.w3.org/Style/Gro…

I suggested that back in 1998…

]]>