Feature Requests

We’re using Marker.io ’s Native Screenshot feature in a React application that contains a PixiJS/WebGL2 canvas. (PixiJS/WebGL2 canvas, React app, Chrome without extension) We’re seeing an intermittent issue where the WebGL canvas is captured as a gray area, while the rest of the page is captured correctly. After investigating, we were able to narrow this down to the initial frames returned by Chrome’s getDisplayMedia() capture stream. Our setup: PixiJS / WebGL2 preserveDrawingBuffer: true is enabled and verified on the actual WebGL2RenderingContext canvas.toDataURL() consistently returns the correct image Chrome’s tab-selection preview shows the WebGL canvas correctly Marker.io Native Screenshot intermittently captures the WebGL area as gray Having Chrome DevTools open appears to prevent the issue We also reproduced the timing behavior independently of Marker.io using navigator.mediaDevices.getDisplayMedia(). Capturing the selected tab at different times after the stream starts produced: 100 ms: WebGL/Pixi area is gray 500 ms: correct 1000 ms: correct 2000 ms: correct This suggests that Chrome’s compositor may need a short amount of time after the capture stream starts before the WebGL layer is available in the captured frames. Feature request It would be great if Native Screenshot could either: wait for a few video frames before extracting the screenshot, ideally using requestVideoFrameCallback(), or provide a configurable native screenshot delay similar to ssr.renderDelay For example: nativeScreenshot: { renderDelay: 500 } Waiting for actual video frames rather than using a fixed timeout would probably be the more robust solution. This would make Native Screenshot capture significantly more reliable for applications using PixiJS, WebGL, games, interactive visualizations, and other GPU-composited canvas content.

Ability to see where other user's bugs on a website have been reported. Similar to a Adobe PDF or a Figma Project, where you can see comments pinned on part of the page/design – would be amazing to see where other users have left feedback to avoid duplicate bugging and saving a ton of time. Bugherd, a competitor of Marker, has this feature and it's been one our team is missing!

I would like Marker to automatically surface performance issues and errors on our website, so we can proactively address them without relying on customer reports.

While testing, I noticed that it would be beneficial to have the ability to decide whether something gets posted as a sub-task or not in Linear. Ideally, this feature would include the option to pass along a few standard attributes such as priority, labels, and assignee.

I need a way to import bugs from an Excel file into the system.

I would like the GitHub integration to map issue types directly to GitHub's native issue type field instead of using labels. This would streamline our workflow by ensuring that issue types from Marker.io are accurately reflected in GitHub.

I would like the ability to enable the AI features only for guests to help them with QA phrasing but not for the internal member of my Marker account.

I want to enhance user experience by customizing the congratulatory message "Congrats for reporting your first feedback." This message is currently not customizable through standard widget settings, and I believe having the ability to tailor it would better align with our branding and user engagement strategies.

I think it would be beneficial if your tool could also function as an anonymous survey and feedback tool. It would be great to have various surveys that could be triggered by different events on the website, allowing us to gather feedback seamlessly.

I wish there was an option to have a simpler experience for some users by submitting a feedback form, not taking a screenshot. This would make it easier for users who may not need to provide detailed visual feedback and prefer a straightforward text-based form.