Michel Mayer
My feedback
46 results found
-
5 votes
An error occurred while saving the comment Michel Mayer
supported this idea
·
-
10 votesMichel Mayer
supported this idea
·
-
30 votesMichel Mayer
supported this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 vote
An error occurred while saving the comment Michel Mayer
commented
Additional clarification:
Overlay slides should behave like normal slides and render exactly as configured in the slide editor. Specifically:
- Automatically applied effects (e.g., box-shadow) should be optional
- Padding should be defined exclusively by the applied design options, not by the overlay container itself
- Background color / transparency should continue to be controlled via the slide settings
- The overlay container should cover 100% of the viewport height (100vh), regardless of the parent slide’s scroll heightThese changes would align overlay behavior with established modal UX standards and improve both functionality and visual consistency across Captivate projects.
Michel Mayer
shared this idea
·
-
3 votes
An error occurred while saving the comment Michel Mayer
commented
Version: 13.0
I would like to support this feature request. Tables are a very common design element in e-learning (comparisons, structured data, checklists, guidelines) and significantly improve the readability of complex information. Currently, there is no native way to create tables in Captivate.
Suggestion:
A native table editor with:
- Header rows
- Footer rows (e.g., totals, sources, legends)
- Table captions (description/summary of the table content, important for screen readers)
- Alignment per column
- Optional responsive layout options (e.g., header stacked above cells on mobile)
- Semantic structure for accessibilityOptional (but highly useful):
- Cell merging (row/column span)
- Proper keyboard navigationSuch functionality would greatly improve quality, workflow, and layout consistency within Captivate.
Michel Mayer
supported this idea
·
-
2 votes
An error occurred while saving the comment Michel Mayer
commented
@Shivang
I’m following up on this feedback because it appears to be a genuine issue with overlay slides on long parent slides.
Version: 13.0
Problem:
When an overlay slide is opened on a long parent slide, the parent slide jumps to the top automatically.Impact:
After closing the overlay, the user loses their previous position and must manually scroll back to continue where they left off.
See screencast: `parent-slide-loses-pos.mp4`Suggestion:
The parent slide should retain its current scroll position when an overlay slide is opened, so that the user’s context is preserved.Michel Mayer
supported this idea
·
-
3 votesMichel Mayer
supported this idea
·
-
4 votesMichel Mayer
supported this idea
·
An error occurred while saving the comment Michel Mayer
commented
I completely understand your frustration. Some posts here remain in a limbo state for extended periods without any visible outcome. The feeling of not being heard is toxic for a feedback platform.
However, from my perspective, the situation could be improved on both Adobe’s side and the community’s side:
What Adobe could improve:
- More transparency on status: Additional labels such as Acknowledged, Won’t Fix, Duplicate, or Under Investigation would show that posts aren’t disappearing into the void.
- Better category structure: Some topics currently have no dedicated category, others appear twice. This makes it harder for users to keep track of recurring themes.
- Occasional status updates: Even short comments like “being reviewed” would help.
- Communicate a broad product direction: Not a detailed roadmap, but general guidance: Which areas currently have priority? Where is the product heading?What the community can contribute:
- Upvote instead of creating duplicates: Consolidated votes make issues more visible.
- Add use cases: Don’t just report an issue — show why it matters.
- Respond to “Need More Info”: Many tickets die because follow-up questions are ignored.Why this matters:
A feedback platform lives on trust. Nobody expects everything to be implemented immediately — but visible activity would be a big step forward. Maybe this thread can be a starting point for evolving the system. It would be a shame if good ideas actually died here. -
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
1 voteMichel Mayer
shared this idea
·
-
2 votesMichel Mayer
shared this idea
·
-
2 votesMichel Mayer
shared this idea
·
-
2 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
·
**Version:** 13.0
I’d like to support this suggestion as well.
**Problem:**
For long-page layouts, there’s still no practical way to place and evaluate multiple quiz questions on a single slide.
A “Quiz Component” — an interactive element with built-in scoring and evaluation — would make building long-page courses much more efficient.
**Example:**
Adapt Framework: https://adaptlearning.github.io/v5demo/#/id/co-15