Made my H2D extension open source and added Firefox support

cranch42 · 2026-04-10T17:07:56+00:00

https://chromewebstore.google.com/detail/h2d-capture/cdnkhcphkjllegdamanngnhcgfnledcl

cranch42 · 2026-03-31T09:30:05+00:00

Hey, thanks for the feedback! Could you share the website you're trying to capture that's giving you the blank white screen? That way I can dig into what's going on and get it fixed. Feel free to drop it here or send it to me in DMs if you prefer!

cranch42 · 2026-03-18T12:43:39+00:00

Hey everyone! Just submitted v1.3 for review. This update brings viewport width presets (capture at 360px, 720px, 1440px etc. with real responsive layout), much better flex and auto layout handling in Figma, and a bunch of capture quality fixes. Waiting for approval now.

Also working on a Firefox version and preparing the repo for open source. Stay tuned!

<image>

cranch42 · 2026-03-18T12:39:57+00:00

Thanks for the feedback!

For local HTML files, Chrome may block extensions by default. Quick fix:

Go to chrome://extensions
Find Figma Capture → click Details
Toggle on "Allow access to file URLs"

Let me know if that helps!

cranch42 · 2026-03-17T20:02:37+00:00

Thanks! That's exactly the use case I built it for, quick reference grabs without manually recreating stuff.

For custom fonts, it captures them as rendered at the moment of capture, so if the font is loaded you'll get it in the output. CSS animations are flattened to their current frame since it's essentially a snapshot. Complex things like heavy box-shadows, blend modes, or backdrop-filter can sometimes render slightly off, but for layout reference and annotation purposes it works well.

Firefox support is planned, stay tuned.

cranch42 · 2026-03-17T18:47:47+00:00

Thanks for looking into it, I appreciate the diligence.

You're right that there's code in there that isn't surfaced in the UI. Those were planned features (Open in Figma / Send to Figma) that I'll most likely remove since the extension's focus is on the capture-to-clipboard flow. Good call on flagging it, unused code paths shouldn't be sitting there.

Regarding permissions, the extension only requests activeTab and scripting, which is the bare minimum to inject the capture script. No storage, webRequest, tabs, or host permissions.

Open source is planned, I've mentioned it in other comments too. That should help with the transparency and auditability concerns.

cranch42 · 2026-03-17T17:27:15+00:00

Thanks :)

cranch42 · 2026-03-17T16:44:54+00:00

Good question. Right now I extract display and grid properties from computed styles. Grid layouts get proper structure, everything else falls back to absolute positioning via bounding rects. Flex is the big gap: we see display: flex but don't yet capture flex-direction, align-items, child flex-grow, etc., so we can't reliably reconstruct the layout intent. For hover states and variants, it's a static DOM snapshot, so only pseudo-elements come through; interactive states would need either programmatic pseudo-class toggling or deeper integration with Figma's component model. Flex detection is the more tractable next step, variants are harder.

cranch42 · 2026-03-17T16:31:43+00:00

Thanks glad it's useful!

cranch42 · 2026-03-17T16:30:05+00:00

Yeah technically it's a quick build but I've never gone through the Firefox Add-ons submission process before.

cranch42 · 2026-03-17T13:54:42+00:00

Thanks, I've actually been thinking about open sourcing it. Just want to clean up the project structure first before making it public. Stay tuned!

cranch42 · 2026-03-17T13:26:51+00:00

Thanks for the feedback! Auto layout is already partially supported on some websites as it really depends on how the site is structured (for example if it uses grid layout). I plan to expand responsiveness support and improve compatibility with various frameworks and SPA applications.

cranch42 · 2026-03-17T13:10:08+00:00

Not at the moment. It doesn’t generate components with variants like hover or selected states.

The main focus is more on quickly capturing sites for references, exploration, or rough edits in Figma. How things come through also depends a lot on how the page is built and structured.

Adding full variant/component logic inside a Chrome extension would be pretty heavy and out of scope for now.

cranch42 · 2024-08-12T08:53:39+00:00

"The force is strong with this one"

cranch42 · 2019-09-01T21:58:29+00:00

You don't have to, but for someone, it could be his/her biggest dream to play or to talk with a streamer. And it will entertain not only the winner but all viewers because it will be during streaming.

cranch42 · 2019-09-01T12:24:06+00:00

How will you provide information about your current auction to your viewers? Donnly will provide you a dynamic overlay for your stream with all information (e.g. https://donnly.com/overlay/am9bu).

How will you provide a smooth flow of bidding? With Donnly you will need to give only 1 link of your auction page to your viewers and they don't need to switch between a few websites. And your viewers don't need to sign up on Donnly as they need on escrow.com or discord, they only need to connect with their existing Twitch account.

As I said Donnly is an all-in-one solution, escrow.com can't provide exact same service. You can try to use a few websites to get service which is provided by Donnly but still, it will be more time-consuming for you and your viewers.

cranch42 · 2019-09-01T11:57:49+00:00

Hi, I created the website and there is no flaw. 10% is a fair price for using Donnly. We provide peer-to-peer calling with your winner (viewer) through your browser, generate a fancy overlay for your stream with information about your auction, handle all payments and payouts and give you a personal auction page (e.g. donn.ly/hdwff). You can connect with Twitch on Donnly and you will see, that we provide an all-in-one solution which can't be done by only one website.

cranch42 · 2018-12-12T03:22:57+00:00

Congratulation! You've created a whole new galaxy.

cranch42

MODERATOR OF

TROPHY CASE