Reading Systems might direct links outside the preview content to a generic placeholder page that indicates the content is not available in the preview, might make such links inactive by removing
their href attributes, or might employ other mechanisms to handle references to non-preview content.
Resources retrieved by scripts may be located outside the EPUB Container, but the [HTML] and [SVG] script elements must not reference Remote Resources to ensure availability at runtime (i.e., from their src or
href attributes, respectively).
I suggested that inactive links could not be accommodated, which is only kind of true, and only to the extent that it's unclear what removing
href attributes from a elements will do to reading systems.
The open question about stripping
the href attributes is what reading systems will do: are they going to explode?
This mention is done by hyperlink tag a using
the href attribute to specify the URL of the page the link goes to.
Audio and video files (and as of 3.1 fonts and remote resources fetched by scripts) are included in the manifest with the full URL to them in the item's
href attribute.
To accomplish this, (1) the Navigation Document [ContentDocs301] must include a nav element which has the epub: type attribute value of index - term - categories, and which contains a complete list of relevant index terms; and (2) the cross-reference in the index must have an epub: type attribute value index - term - category and
an href attribute value pointing to that list.
A locator typically has an [HTML5]
href attribute pointing to some location within the EPUB Publication; when it has no
href attribute value, the locator will not be actionable.
The values of
the href attribute should be a Uniform Resource Identifier (URI) that is relative to the OPF file.
You will notice that
the href attribute uses relative paths to declare where the files are located.
Each a has
an href attribute value pointing to that term's entry in the index document.
' The relative IRI reference provided in
the href attribute of the a element must resolve to an EPUB Content Document or fragment therein.
It is a non-actionable cross-reference as shown by the absence of
an href attribute:
Removing
the href attribute is perfectly valid to the navigation document requirements, but whether developers have accounted for links without href attributes is another matter.
Common hyperlinking mechanisms include
the href attribute of the [HTML] a and area elements and scripted links (e.g., using DOM Events and / or form elements).
Each item element in the manifest identifies a Publication Resource by the IRI [RFC3987] provided in
its href attribute.
If the epub: rendition attribute is used to specify the target Rendition, any fragment identifier scheme may be used within the URI value of
the href attribute of a elements (e.g., unique identifier, or W3C Media Fragment).
Each a element must specify which Rendition it refers to either 1) by including an Intra-Publication CFI [EPUBCFI] in
its href attribute, or 2) by providing the relative path to the Package Document for the Rendition as the value of an epub: rendition attribute.
The metadata element may contain zero or more link elements, each of which identifies the location of a linked resource in its required
href attribute
In this case, the matching content may be identified by an IRI provided in
the href attribute.
When
no href attribute is present, the match element represents search keys matching the entire dictionary entry or glossary term referenced by its search - key - group parent.
Within search - key - group or match elements, the IRI value of
an href attribute is a relative IRI identifying a location within an EPUB Content Document, and is resolved against the base IRI of the Search Key Map Document.
If the Search Key Map Document is part of an EPUB Dictionary, the IRI provided in
the href attribute must identify the element — carrying an implied or explicit dictentry epub: type property — that represents the related entry in the Content Document.
The IRI value of
the href attribute must be relative.
The IRI expressed in
the href attribute may include a fragment identifier but must not include EPUB canonical fragment identifiers [EPUBCFI].
Not exact matches
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these < abbr title ="HyperText Markup Language"> HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes a
href title.
Each item is defined with the following
attributes: id,
href, and media - type.
Everything after an
href or src
attribute is a reference to a file within the ebook's file structure.
If a Processing Agent renames files, it is responsible for also ensuring that all references to the original names are updated in all resources (all
href and src
attributes in XHTML Content Documents, any linked CSS and @import rules, etc.).
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">
You may use these HTML tags and
attributes: < a
href =""title =""> < abbr title =""> < acronym title ="">
< blockquote cite =""> < del datetime =""> < q cite ="">