Quote:
Originally Posted by jhowell
|
Yeah, I saw this and read and re-read it multiple times. Perhaps (from years of dealing with formal language specs) I tend to read things a bit too closely from time to time (
), but I interpreted this as a
constraint on footnotes -- however they are implemented. And moreover, as an informative comment on the use of the <aside> element.
So I saw the
requirement for bidirectional links in footnotes and said to myself "Okay. Roger that." And then "But then how do I
implement the popup?" To what, exactly, do I apply this constraint?
The next sentence in that paragraph is of no help in answering that question since it says only that
some Kindle devices will
display footnotes having bidirectional hyperlinks as popups. But it's still nowhere said what a footnote
is. Nor is any characteristic example given.
Is
any construct in which there's a bidirectional hyperlink interpreted by the device as a "footnote" and rendered as a popup? That seems a bit goofy. Then something is a footnote (or regarded by "some Kindle devices" as a footnote) if and only if it contains a bidirectional hyperlink? Then I could never have anything with a bidirectional hyperlink which on such a device would
not be rendered as a popup? Not exactly ANSI- or ISO-level description of a language/implementation feature.
Hence my confusion. Apparently I missed the "obvious".
But now at least I have a good experimental environment and good pointers to what should work.
