Michel Mayer
My feedback
29 results found
-
1 vote
An error occurred while saving the comment Michel Mayer
shared this idea
·
-
5 votesMichel Mayer
supported this idea
·
-
3 votesMichel Mayer
supported this idea
·
-
2 votesMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
5 votesMichel Mayer
supported this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
2 votesMichel Mayer
shared this idea
·
-
1 vote
An error occurred while saving the comment Michel Mayer
commented
[Response to “Need More Info”]
Thanks for checking. According to the official documentation, the property videoHeight should apply to video card containers:
Applies to only video card container. This defines the height of the video object in the content block.
Example:```json
{"tag": "videoCard",
"customStyles": { ... },
"customProperties": {
"videoHeight": 400
}
}
```However, even when defining videoHeight (e.g. "videoHeight": 500) in the designOption.json, the value is ignored, and Captivate injects a fixed inline height into the container at runtime.
```html
<div id="videoContainer_si104665" class="videoContainer" data-desktop-height="400" automation-id="slidevideo:::container_aspectratio" style="aspect-ratio: 1.77778 / 1; height: 400px; max-width: 100%;">
```It would be great if this property could also be supported for "container-video-grid-card" elements (used in Video Grids), and if both absolute (px) and relative (100% / auto) values were accepted.
This would allow fully responsive video layouts directly via JSON, without relying on hardcoded inline heights.
Michel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
18 votesMichel Mayer
supported this idea
·
-
3 votesMichel Mayer
supported this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
4 votesMichel Mayer
supported this idea
·
[Response to “Need More Info”]
Thanks for checking. Here’s a screen recording that demonstrates the behavior in more detail:
In the video, you can see a Tabs widget, followed by an Accordion widget below it.
1. When the preview starts, the first tab in the Tabs widget is active and highlighted in black.
2. I click Tab 2 → Tab 2 becomes highlighted correctly, and its content is displayed.
3. I click Tab 3 → Tab 3 becomes highlighted correctly, and its content is displayed.
4. Now I click the first section of the Accordion widget below.
- The Accordion content opens as expected.
- However, at this moment, the black highlight of Tab 3 disappears in the Tabs widget.
- The content of Tab 3 is still visible, but there is no visual indication of which tab is currently selected.