Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

itts:forcedDisplay should apply to image element in image profile #493

Open
skynavga opened this issue Sep 29, 2019 · 9 comments
Open

itts:forcedDisplay should apply to image element in image profile #493

skynavga opened this issue Sep 29, 2019 · 9 comments

Comments

@skynavga
Copy link
Contributor

No description provided.

@palemieux
Copy link
Contributor

palemieux commented Oct 10, 2019

itts:forcedDisplay already applies to div so I do not think this is necessary.

@nigelmegitt
Copy link
Contributor

@skynavga we'd like to be able to resolve this before or during Thursday's call if possible.

@skynavga
Copy link
Contributor Author

but div is not image

@palemieux
Copy link
Contributor

Applying itts:forcedDisplay to the parent div of an image has the effect as applying it to image (for Image Profile document).

@skynavga
Copy link
Contributor Author

ok, but an author should be able to apply it to the image itself alone, yes?

@palemieux
Copy link
Contributor

ok, but an author should be able to apply it to the image itself alone, yes?

Not necessary in IMSC, and itts:forcedDisplay is an IMSC extension.

My overriding suggestion is to avoid making any change to the Image Profile unless absolutely necessary.

@nigelmegitt
Copy link
Contributor

ok, but an author should be able to apply it to the image itself alone, yes?

@skynavga It'd be helpful to know what's driving this request - for example are there users or practitioners who have been in touch with you to complain about this omission? If it's a point of principle alone, I don't disagree that in an ideal world the semantic makes more sense if we could apply forcedDisplay directly to the image, but I would also back @palemieux 's thinking that we have a way to achieve the same effect and that making changes to the Image Profile is something we should be super reluctant to do without a strong motive, i.e. I'd also do nothing.

@skynavga
Copy link
Contributor Author

No, there was no external input. This came up during work on TTV support for IMSC1.1 and review of upcoming IMSC1.2 semantics w.r.t. semantic symmetry and consistency.

@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed itts:forcedDisplay should apply to image element in image profile imsc#493, and agreed to the following:

  • RESOLUTION: We will not address this in IMSC 1.2 but leave on the backlog for potentially fixing in some future version.
The full IRC log of that discussion <nigel> Topic: itts:forcedDisplay should apply to image element in image profile imsc#493
<nigel> github: https://github.com//issues/493
<nigel> Pierre: This is a direct parallel to #490. forced Display applies to div and not image.
<nigel> .. This is fine in Image profile because there's a 1:1 mapping between images and divs, so I suggest the same
<nigel> .. disposition, which is not to address in IMSC 1.2 but leave on the backlog.
<nigel> Nigel: I took the step for this one of checking in with Glenn on the driver for the issue and it seems
<nigel> .. to be one of semantic asymmetry and inconsistency. I take the view also that this inconsistency is not great
<nigel> .. but is not enough of a motivation in itself to make a change at this time.
<nigel> PROPOSAL: We will not address this in IMSC 1.2 but leave on the backlog for potentially fixing in some future version.
<nigel> Nigel: Any objections?
<nigel> group: [no objections]
<nigel> RESOLUTION: We will not address this in IMSC 1.2 but leave on the backlog for potentially fixing in some future version.

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

No branches or pull requests

4 participants