Skip to content

Media overlay fragments - #1663

Merged
dauwhe merged 7 commits into
mainfrom
fix/issue-1586
May 6, 2021
Merged

Media overlay fragments#1663
dauwhe merged 7 commits into
mainfrom
fix/issue-1586

Conversation

@mattgarrish

@mattgarrish mattgarrish commented May 5, 2021

Copy link
Copy Markdown
Member

Here's my best attempt at resolving #1586.

I've added a new section to the authoring spec specifically dealing with fragment identifiers and have linked down to it from the textref and src attributes.

I've specified that authors should reference a target element or use an svg fragid, but may use other schemes (noting that support is not required).

In the reading system specification, I've made the recommendation to ensure the element is visible contingent on one of the above two fragment identifier schemes being used.

Otherwise, I've made some minor cleanup to ensure we're not being too element-specific when talking about the fragments (plus some general cleanup since I was reading through the sections anyway).

Fully expect this will need some more tweaking, though. I'll add a change log entry once it's clear what we're settling on.

Fixes #1586


Preview | Diff

@dauwhe dauwhe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that this references HTML and (indirectly) the URL spec.

Comment thread epub33/core/index.html
Comment thread epub33/core/index.html
Comment thread epub33/core/index.html
Comment thread epub33/core/index.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Is reference to xpointer shorthand for fragment identifiers too restrictive?

5 participants