Newbie question about <Styles> and tooltips

[JackTrade]

I frequently run into this problem - trying to implement a style by including the <Style> section inline with the HTML code (Section0001,xhtml), works the way it's supposed to.

Placing the <Style> section in a blank stylesheet (Style0001.css), however, doesn't. For example, trying to form tooltips using code from https://chrisbracco.com/a-simple-css-tooltip/ or from http://netdna.webdesignerdepot.com/u...ltip_demo.html works only when the Style is inline.

I have also encountered this problem with styles unrelated to tooltips.

Any idea why?

Thanks.

[theducks]

because, <style> is a special inline tag pair that signifies the contents is a stylesheet

You link stylesheets, the link specifies what type of link

Sigil does all the dirty work for you. Right-click the filename (to link): Select 'Link Stylesheets: TICK all that apply (those that are NOT ticked will unlink): apply

That is it

[JackTrade]

Originally Posted by theducks

You link stylesheets, the link specifies what type of link

Sigil does all the dirty work for you. Right-click the filename (to link): Select 'Link Stylesheets: TICK all that apply

It seems to work! Thanks!

I didn't realize that I have to actively link Stylesheets which are part of the same document as the HTML page...

[DiapDealer]

Originally Posted by JackTrade

I didn't realize that I have to actively link Stylesheets which are part of the same document as the HTML page...

Did you, perhaps mean, "part of the same EPUB"? I only ask because you don't have to link styles that are part of the same HTML page. You only have to link stylesheets to html pages when they ARE, in fact, separate documents/files.

[JackTrade]

Originally Posted by DiapDealer

Did you, perhaps mean, "part of the same EPUB"? I only ask because you don't have to link styles that part of the same HTML page. You only have to link stylesheets to html pages when they ARE, in fact, separate documents/files.

That's exactly what I meant - same EPUB. Just for background - what I did was go to https://chrisbracco.com/a-simple-css-tooltip/, which has separate codes for the HTML and the CSS. I first copied the CSS, opened Sigil and, in a new EPUB, pasted the CSS code in an HTML sheet; went back to the site, copies the HTML code, back to Sigil, pasted the HTML code in the same HTML sheet as the CSS - and it all worked.

Test 2 - created yet another new EPUB in Sigil. Pasted the HTML code in a new HTML sheet; then went to Add/Blank Stylesheet, pasted the CSS code in that new Stylesheet: this time it didn't work.

Finally, using the advice above, went to the HTML sheet, clicked on Link Stylesheets, linked the new Stylesheet - and, lo and behold, it worked again!

As I mentioned, it doesn't make sense to me that Sigil won't do the linking by itself (to Styles in the same EPUB), but this is where it seems to be.

[DiapDealer]

Originally Posted by JackTrade

As I mentioned, it doesn't make sense to me that Sigil won't do the linking by itself (to Styles in the same EPUB), but this is where it seems to be.

Since an epub can be comprised of numerous html files as well as numerous css files, how on earth would Sigil know which css you wish to apply to which html?

[Notjohn]

Since there are circumstances when your style pointer might not appear in all files (for example, if you split the epub before you think to add the style sheet), you might find it useful to save a working link. This is mine, by way of example:

<link href="../Styles/epub.css" rel="stylesheet" type="text/css"/>

[JackTrade]

Originally Posted by Notjohn

Since there are circumstances when your style pointer might not appear in all files (for example, if you split the epub before you think to add the style sheet), you might find it useful to save a working link.

Sorry, but as a newbie, I have to ask: so you would add this link in each HTML file in the EPUB?

[theducks]

Originally Posted by JackTrade

Sorry, but as a newbie, I have to ask: so you would add this link in each HTML file in the EPUB?

That needs to use it
Again, Sigil will do that code for you if you don't want to 'type'

[GrannyGrump]

You might have several CSS stylesheets, and you might not want to use every one on every html file. For instance, you might have a stylesheet named Main.css that you use for each file that is in the body of the book. Then you might have an additional special one named Aux.css that you want to use only for a single html file that contains your Index. Maybe you only have three html files that include images, so you might want another special stylesheet named Pics.css containing only stylings for your illustrations, so you could link that one only to those three html files. Etc, etc, etc.

Each (x)html file can be linked to multiple stylesheets.

[Toxaris]

Originally Posted by JackTrade

As I mentioned, it doesn't make sense to me that Sigil won't do the linking by itself (to Styles in the same EPUB), but this is where it seems to be.

Perhaps it makes sense if I tell you that you can have multiple stylesheets. Sometimes it is easier to have stylesheets separate for certain HTML files. If they were automatically linked, it can cause strange effects. Some pages don't need a stylesheet at all.

[DiapDealer]

Originally Posted by Toxaris

Perhaps it makes sense if I tell you that you can have multiple stylesheets. Sometimes it is easier to have stylesheets separate for certain HTML files. If they were automatically linked, it can cause strange effects. Some pages don't need a stylesheet at all.

And since Sigil has no idea if the css file you just added is the one-and-only, or only the first-of-many, it wouldn't make sense to automatically link it to every html file.

[JustinThought]

Originally Posted by DiapDealer

And since Sigil has no idea if the css file you just added is the one-and-only, or only the first-of-many, it wouldn't make sense to automatically link it to every html file.

I've got that going on in something I'm working on now. I have a specific style I've gotten from somewhere else on this forum, and during testing I placed it into a separate stylesheet (for some reason--it seemed to be the thing to do at the time). That style is used in only about five or six chapters out of the book, so I have only linked that sheet to those chapters.

So my question is, is there a speed issue here? Could linking that unused stylesheet--or copying those specific styles into my main stylesheet--cause some slowdown in the overall epub? --Or the inverse, could copying that style into my main stylesheet and deleting the "extra" one speed up the the process?

I've been curious about this because my I re-use the same stylesheet in every epub I do, and it has styles that are often not used in that specific book. And I don't go out of my way to delete the unused styles at the end of development. So am I setting a little "time"-bomb here?

[exaltedwombat]

Have you ever experienced an eBook that you felt responded particularly slowly?

[Turtle91]

Originally Posted by exaltedwombat

Have you ever experienced an eBook that you felt responded particularly slowly?

Most definitely...but they were ones that were immense...50mb or so (if I remember correctly) and filled with a ton of junk code (bloat). After I cleaned it up it was a much more manageable size - just under 2mb - and was quite spry.

As far as extra css files slowing it down: Yes. Any extra action that the app has to take will slow it down...be it from opening extra css sheets or wading through bloated inline styles/spans...but we're talking micro-seconds here for opening a css sheet. There would need to be a ton of css's linked to each html to make it noticeable. In this particular case having a few extra css sheets shouldn't slow it down noticeably because they are only referenced on the few pages that need them and would only be accessed by the app when those html files are opened.

Having said all that, I find that having all my css on a single sheet makes it easier for me to keep myself organized. I would get confused if there were multiple sheets, and possibly different sheets using the same names. *shudder*

I keep all of my standard css at the top of the sheet and then book specific styles at the bottom where they would override the standard style higher on the sheet. After I'm done editing, I use the "Delete Unused Stylesheet Classes" tool to...um... delete unused stylesheet classes and leave my CSS sheet as tidy as possible. note: when using this tool carefully check the list before deleting - it sometimes doesn't pick up on pseudo-elements being used properly.