When you bring a Flex link into MarkUp, you may notice some unexpected behaviour. The MarkUp team is actively working on improvements to better support the more complex elements within Flex. Native commenting within Flex is currently in development and is scheduled for release in Q4 2025.
In the meantime, here are some known behaviours and recommendations when viewing or commenting on Flex experiences within MarkUp:
Pin Accuracy
When proxying a Flex experience, pin placement may appear offset by around 5%, depending on the layout complexity. This variance can increase with advanced design features such as parallax scrolling.
Recommendation:
Use the MarkUp Screenshot functionality to get a precise view of where a pin was originally placed.
Clicking on Pins
In some cases, clicking directly on a pin may not display the associated feedback. This can happen when pin placement is slightly inaccurate, meaning the pin is no longer perfectly linked to its intended position.
If this occurs, try clicking near the pin or use the comment list in the sidebar to view the feedback associated with that pin. This ensures you can still access all context even if the visual pin response is misaligned.
Chrome Extension
We recommend using the MarkUp Chrome Extension, available in the Integrations section.
The Chrome extension captures screenshots instantly upon pin placement, improving both accuracy and responsiveness. When using MarkUp without the extension (via proxy), there may be a slight delay in screenshot capture.
Parallax Scroll Elements
If your Flex experience includes parallax scroll, you may encounter the following:
Pin Placement Inaccuracy:
Our current pin logic does not yet account for parallax movement, making it difficult to anchor pins precisely to a single element.
Click-to-Location Limitations:
When clicking a pin from the sidebar, MarkUp normally scrolls directly to that pin’s location. However, in experiences using parallax scroll, MarkUp may be unable to move past certain elements. Pins placed after these sections might not be automatically located when using the click-to-location function.
Duplicate Headers Displayed
In some complex Flex experiences, two headers may appear when switching between variants. This behaviour is known and is currently being investigated by our development team.
Looking Ahead
We’re aware of these limitations and are working to deliver a smoother, more accurate experience for all Flex users. Enhanced Flex compatibility, including native commenting, is planned for release in Q4 2025.
We appreciate your patience and understanding as we continue to refine the experience and expand MarkUp’s support for advanced Flex-based designs.