stylesheet.CSS anyone? - Page 6

JSWolf · 12-25-2015, 04:42 AM

Quote:

Originally Posted by ProDigit

They might be able to access TOC, but with a link you can redirect to the Index,
which, in cases of a lot of links, or certain structures, could be more useful than a TOC, or have better layout.

Just put an index entry in the ToC. Problem solved. There is very little to no need for chapter headers to be links. Old Readers also have quick access to the ToC. So it's not something you need to do for people with older Readers.

phillipgessert · 12-25-2015, 09:34 AM

I think visible links could encourage navigation more than the inbuilt TOC does, so in some cases using them could be a valid design decision.

Turtle91 · 12-25-2015, 08:34 PM

Quote:

Originally Posted by JSWolf

I think it's poor style to do so. It makes the headers blue (color screen) and underlined. ....

Try:
a {color:inherit; text-decoration:none}

Does that not work in your RMDSK??

In everything else I've tried it makes it look like the rest of the text. I'm not saying that it should be coded that way...simply saying that you have control over what links look like.

Toxaris · 12-26-2015, 04:26 AM

Quote:

Originally Posted by Turtle91

Try:
a {color:inherit; text-decoration:none}

Does that not work in your RMDSK??

In everything else I've tried it makes it look like the rest of the text. I'm not saying that it should be coded that way...simply saying that you have control over what links look like.

I seem to recall that the underline cannot be removed this way for links, at least not on all readers. Not sure though, I never use links like that.

JSWolf · 12-26-2015, 04:51 AM

Quote:

Originally Posted by Toxaris

I seem to recall that the underline cannot be removed this way for links, at least not on all readers. Not sure though, I never use links like that.

Yes, you can remove the underline, but on an eInk screen, the CSS that Turtle91 posted is next to useless. You won't see that the headers are links and that makes the links useless and just code bloat. A link you cannot see is a link is no good.

Jellby · 12-26-2015, 05:02 AM

Some links are "obvious", like entries in an inline TOC, or footnotes: I'd expect those to be links and "click" on them (if I wanted to follow the link), underline or not. Others could be explained in an "about this ebook" section, or left as a kind easter-egg for the inquisitive user; if someone cannot be bothered to read the instructions, well, bad luck for him, he can still read the text normally, nothing is lost.

JSWolf · 12-26-2015, 01:43 PM

If I see the headers setup as links, I remove the <a code as it's not needed. 3 taps and I have the ToC on screen.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Converting cm to em in css stylesheet	roger64	ePub	41	06-13-2014 01:00 PM
Question: Find/Replace in css stylesheet	ElMiko	Sigil	12	12-25-2011 06:29 AM
ePub margins : @page vs stylesheet.css	Agama	Calibre	1	08-16-2010 04:37 PM
How to maintain a global CSS stylesheet	amoroso	Sigil	7	07-18-2010 08:37 PM
Where is the stylesheet.css?	roger64	Sigil	4	03-23-2010 02:12 PM

12-25-2015, 09:34 AM	#77
phillipgessert Addict Posts: 318 Karma: 3200000 Join Date: Oct 2015 Location: Madison, WI Device: Kindle 5th Gen	I think visible links could encourage navigation more than the inbuilt TOC does, so in some cases using them could be a valid design decision.

12-26-2015, 05:02 AM	#81
Jellby frumious Bandersnatch Posts: 7,558 Karma: 19620479 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	Some links are "obvious", like entries in an inline TOC, or footnotes: I'd expect those to be links and "click" on them (if I wanted to follow the link), underline or not. Others could be explained in an "about this ebook" section, or left as a kind easter-egg for the inquisitive user; if someone cannot be bothered to read the instructions, well, bad luck for him, he can still read the text normally, nothing is lost.

12-26-2015, 01:43 PM	#82
JSWolf Resident Curmudgeon Posts: 79,939 Karma: 146918083 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	If I see the headers setup as links, I remove the <a code as it's not needed. 3 taps and I have the ToC on screen.