We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2016-08-17 16:58:16 +0200 |
Most (all?) browsers by default identify visited links. Firefox uses a purple-ish colour by default. Most modern sites override that in CSS so it's not as common to see this as it once was. But I regularly use a site - http://mudcat.org - which dates from the 1990s and I really need this 'visited' colour to identify new posts.
The browser on my Jolla C (2.0.2.43) doesn't colour visited links on mudcat.org. I think that's a bug - and I'll raise an issue on github if that's confirmed. So I wrote a userstyle to correct it for mudcat. (I have several other userstyles, including for mudcat, so I know that userstyles work. Put them in ~/.mozilla/mozembed/chrome/userContent.css). This one works in Firefox desktop but it doesn't work on the Jolla C:
@-moz-document url("http://mudcat.org/")
/* mudcat index - jolla-only */
/* Version 1 14-8-2016 */
{
/* Visited links */
td :visited {color:purple};
}
Even
:visited {color:purple};alone doesn't work.
So I suspect that it's not just that the browser doesn't colour links by default but that the :visited pseudoclass doesn't work at all.
Questions:
2 | No.2 Revision |
Most (all?) browsers by default identify visited links. Firefox uses a purple-ish colour by default. Most modern sites override that in CSS so it's not as common to see this as it once was. But I regularly use a site - http://mudcat.org - which dates from the 1990s and I really need this 'visited' colour to identify new posts.
The browser on my Jolla C (2.0.2.43) doesn't colour visited links on mudcat.org. I think that's a bug - and I'll raise an issue on github if that's confirmed. So I wrote a userstyle to correct it for mudcat. (I have several other userstyles, including for mudcat, so I know that userstyles work. Put them in ~/.mozilla/mozembed/chrome/userContent.css). This one works in Firefox desktop but it doesn't work on the Jolla C:
@-moz-document url("http://mudcat.org/")
/* mudcat index - jolla-only */
/* Version 1 14-8-2016 */
{
/* Visited links */
td :visited {color:purple};
}
Even
:visited {color:purple};alone doesn't work.
So I suspect that it's not just that the browser doesn't colour links by default but that the :visited pseudoclass doesn't work at all.
Questions:
https://github.com/sailfishos/sailfish-browser/issues/500
Edit 1: 9-10-2016
Bug still present in 2.0.4 browser.
3 | No.3 Revision |
Most (all?) browsers by default identify visited links. Firefox uses a purple-ish colour by default. Most modern sites override that in CSS so it's not as common to see this as it once was. But I regularly use a site - http://mudcat.org - which dates from the 1990s and I really need this 'visited' colour to identify new posts.
The browser on my Jolla C (2.0.2.43) doesn't colour visited links on mudcat.org. I think that's a bug - and I'll raise an issue on github if that's confirmed. So I wrote a userstyle to correct it for mudcat. (I have several other userstyles, including for mudcat, so I know that :visited in userstyles work. Put them in ~/.mozilla/mozembed/chrome/userContent.css). This one works in Firefox desktop but it doesn't work on the Jolla C:
@-moz-document url("http://mudcat.org/")
/* mudcat index - jolla-only */
/* Version 1 14-8-2016 */
{
/* Visited links */
td :visited {color:purple};
}
Even
:visited {color:purple};alone doesn't work.
So either, so I suspect that it's not just that the browser doesn't colour links by default but that the :visited pseudoclass doesn't work at all.
Questions:
**Update: 16-3-2017
I looked into this, so I'll record what I concluded.
Firefox (gecko) stores history in places.sqlite in the profile along with
otherSo the failure to effect :visited isn't a bug so much as a result of a design decision. To fix
ithttps://github.com/sailfishos/sailfish-browser/issues/500
Edit 1: 9-10-2016
Bug still present in 2.0.4 browser.would require the css computation to point to the new history database.
4 | No.4 Revision |
Most (all?) browsers by default identify visited links. Firefox uses a purple-ish colour by default. Most modern sites override that in CSS so it's not as common to see this as it once was. But I regularly use a site - http://mudcat.org - which dates from the 1990s and I really need this 'visited' colour to identify new posts.
:visited in userstyles doesn't work either, so I suspect that it's not just that the browser doesn't colour links by default but that the :visited pseudoclass doesn't work at all.
https://github.com/sailfishos/sailfish-browser/issues/500
**Update: Update: 16-3-2017
I looked into this, so I'll record what I concluded.
Firefox (gecko) stores history in places.sqlite in the profile along with other stuff, notably bookmarks and favicons. The Jolla browser has no places database. It stores history in /home/nemo/.local/share/org.sailfishos/sailfish-browser/sailfish-browser.sqlite (table: browser_history). It stores bookmarks in bookmarks.json in the same directory.
So the failure to effect :visited isn't a bug so much as a result of a design decision. To fix it would require the css computation to point to the new history database.
5 | retagged |
Most (all?) browsers by default identify visited links. Firefox uses a purple-ish colour by default. Most modern sites override that in CSS so it's not as common to see this as it once was. But I regularly use a site - http://mudcat.org - which dates from the 1990s and I really need this 'visited' colour to identify new posts.
:visited in userstyles doesn't work either, so I suspect that it's not just that the browser doesn't colour links by default but that the :visited pseudoclass doesn't work at all.
https://github.com/sailfishos/sailfish-browser/issues/500
Update: 16-3-2017
I looked into this, so I'll record what I concluded.
Firefox (gecko) stores history in places.sqlite in the profile along with other stuff, notably bookmarks and favicons. The Jolla browser has no places database. It stores history in /home/nemo/.local/share/org.sailfishos/sailfish-browser/sailfish-browser.sqlite (table: browser_history). It stores bookmarks in bookmarks.json in the same directory.
So the failure to effect :visited isn't a bug so much as a result of a design decision. To fix it would require the css computation to point to the new history database.