Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#1998 closed Defect (Won't Fix)

Visited links not marked

Reported by: anonymous Owned by: timothy
Component: Colloquy (Mac) Version: 2.3 (Mac)
Severity: Normal Keywords: css, a:visited, visited, links, style
Cc: mail.temc@…

Description

Hi,

I've used a custom CSS-file to change the default styleing a it.

In particular the style for the "a" selector and the "a:visited" selector.
As it turns out, Colloquy does not support the :visited selector ? (correct me I'm wrong)

I consider this a serious lack since in various occasions it's almost unworkable without any indication as to what's visited and what not.

--
TeMc?

Change History (4)

comment:1 Changed 10 years ago by timothy

  • Resolution set to wontfix
  • Status changed from new to closed

We can't fix this. The visited info is tracked by your web browser (Safari, Firefox, Opera, etc.) We don't have access to that info.

We could support :visited automatically via WebKit? — if Colloquy was a web browser.

You will find this is true in any other Mac application, they have no way to show visited links in a different style.

Sorry we can't meet your needs.

comment:2 Changed 10 years ago by TeMc

  • Resolution wontfix deleted
  • Status changed from closed to reopened

It may not work as in keeping a browser history.

But I believe it's incredibly easy to deterimine wheter a link has been clicked or not in the application. Whether it has been browser before by the (default) webbrowser is irrelevant.

What I think is most important is to see what links were clicked.
Especially in for example a channel with report-robots for a project that has many updates per minute/second. Just being able to differentiate what links were previously clicked would already be a blessing.

If really not thinking of a solution, then atleast try this:

Any clicked link:

  • Get href and open in default browser (already in Colloquy)
  • Set/add classname of "visited" or "clicked" to the <a>anchor-tag.

comment:3 Changed 10 years ago by zach

  • Resolution set to wontfix
  • Status changed from reopened to closed

It might be technically possible to do this with a hammer and lots of time, but, a hammer isn't the best tool to use for this job. It would actually do more harm then good.

Doing it your way wouldn't be integrated with the rest of the system (Safari/Firefox?/whatever other web browser you have, to keep everything in sync).

There are also problems for privacy; when you clear everything in Safari, its easy to do so and you know what it does. Doing the same in Colloquy is more difficult your way; especially if you have to parse every logfile (which can get quite big) to remove the attributes. Should /clear or the clear button remove these attributes from the log as well?

comment:4 Changed 10 years ago by Robby

  • milestone Colloquy 2.4 deleted
Note: See TracTickets for help on using tickets.