Bug #70882
closed
fluid_styled_content textmedia CE – width of video elements not available
Added by Jeff C over 8 years ago.
Updated about 8 years ago.
Category:
Fluid Styled Content
Description
When inserting fluid_styled_content's new textmedia content element the output contains the values column.dimensions.width and column.dimensions.height, which store the dimensions of the used media elements.
However, when used with videos, both values are empty. Trying to work around this issue by setting the dimensions manually in tab "appearance" only leads to column.dimensions.height to be filled. column.dimensions.width always stays at '0'.
- Status changed from New to Needs Feedback
Hi, Jeff
the {column}
contains the already calculated values. If you just state a width it will be present here. If you give a height, only that value is used to scale the media object to a dynamic width. If you want to access the values, you set in your content element in the appearance tab, you can always access those values within your template with {data.imagewidth}
and {data.imageheight}
.
Does this solve your issue?
Probably you run into the issue that TYPO3 doesn't know a width/height for your video. Maybe we can somehow come up with a fallback for when the asset has no dimensions given.
I'm okay with typo3 not having the natural width and height of a video, however what should work is that I should be able to add static values under "appearance". I suppose that this is how it should work. The manually entered width-value just does not get transferred to the template.
What kind of video type are you using? I did some test with all allowed video types and they scale to the defined dimension.
Can you report the steps you followed to reproduce this issue? As far as I can see, the textmedia element only allows .mp4 and .webm extensions.
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Benni Mack)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF