Tony GorbProduct Designer & Builder

I’d love to join a product team for the long run and help build what comes next.

Optimind closed in October 2026.


View CV
LinkedIn (opens in a new tab)GitHub (opens in a new tab)

My design tool felt sticky. A floating toolbar was why.

Clicking text in my design tool felt sticky. I blamed the right thing, measured it in the wrong browser, and threw the fix away. Then I measured where my users actually click.

In this story3 sections
  1. The first guess
  2. The wrong browser
  3. Drawing the toolbar inside

I was building a design tool, and clicking a text layer felt sticky. Not broken. Just a beat late, like the app had to think about it. A designer feels that before they can name it, and I couldn't let it go.

The canvas in my tool is an iframe. The panels around it, Layers on the left and the Inspector on the right, are the main page. After every click the panels redraw, and in development that took 55 to 80 ms. Fine on its own. The problem was the next click.

The first guess

My first guess was the toolbar. It floated over the bottom of the canvas, the way Figma's does, and a few other bits hung over the frame's edge too. When something clickable sits on top of an iframe, the browser can't hand the click straight to the frame. It has to ask the page underneath where the click landed, and if that page is busy redrawing, the click waits.

So I built a bare test page with the same canvas and nothing on top. Clicks went through in 0.7 ms. With the overlap and a busy page: 259 ms. Case closed, I thought.

I moved the toolbar into its own strip under the canvas, so nothing covered the frame. Zero elements on top. Measured again. 259 ms. Exactly the same.

So I put the toolbar back where it was and called the overlap innocent.

The wrong browser

That was the wrong turn. The idea was right; the instrument was lying. I had been measuring in the browser my test runner ships with. That browser runs the canvas frame on the same thread as the page around it, so any redraw blocks any click, overlap or not. Your Chrome doesn't work that way. In real Chrome, the frame gets its own lane, unless something sits on top of it and forces the detour.

Drawing the toolbar inside

Measured in real Chrome, the overlap was the whole story. The fix was to stop floating the toolbar over the canvas and draw it inside the canvas instead: same look, same icons, same place on screen, but now part of the frame itself. The toolbar tells the panels which button was pressed, and the panels tell it what to show. Its menus still open from the page, and only while they're open.

A click reaching the canvas
1 msfrom 259 ms
Click to selection box
13 msfrom 272 ms

From click to selection box went from 272 ms to 13 ms. Text stopped feeling sticky. One case stayed slow on purpose: the click that closes an open toolbar menu still waits, because for that moment the menu really is on top. Every click after it is fast again.

If your product has a canvas in an iframe, whether that's an editor, a preview or a map, don't float clickable UI over it. Draw the controls inside the frame or beside it. And measure input lag in the browser your users actually use. The test browser was the reason I threw away a correct fix.

Tony Gorb, Product Designer & Builder

Questions about this story, or a design role to talk about? Write to bytonygorb@gmail.com or find me on LinkedIn.

More stories