View Single Post
Old 06-29-2016, 12:45 AM   #23
capidamonte
Not who you think I am...
capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.capidamonte can even cheer up an android equipped with a defective Genuine Personality Prototype.
 
capidamonte's Avatar
 
Posts: 374
Karma: 30283
Join Date: Jan 2010
Location: Honolulu
Device: PocketBook 360 -- Ivory
I'm not expert enough to answer the following question, nor in a position to experiment but... as long as there was no more than one link to the common target from a single html page (ie: in the chapter) could you link in a different css for each chapter with a different set of css variables? (If there was more than one link in the chapter, you'd only be able to pick one variable to come back to even with this hacky idea.)

Then if there was no css linked in the target's html, could it inherit the css of the preceding html page? If so, you could set the variables in the chapter's linked css and the target's html would use them.

So, in every chapter that you want a different return value you vary that value in the css variable.

Probably wouldn't work, but if there is a way to force that inheritance, it might. @import, maybe? I'm probably way off base here -- surely when you jump between an epub's internal documents, all prior css is lost...

2¢, and worth every penny.

Aloha.

ps: @document in your master css with nested anchor tags for every origin link at the target? So when you leave chapter 17 for the target html you link to its <a href="target.html#chapter17"> anchor, and your CSS variable gets applied? I don't know if the URL can include anchors for @document. ... or maybe a unique string in that anchor, and use the regexp function of @document?

pss: I bet variables don't work in most devices anyway.

psss: @document and symbolic links?

Last edited by capidamonte; 06-29-2016 at 01:20 AM. Reason: addendum
capidamonte is offline   Reply With Quote