autofirmer-expanded

Files

T

Brandon LiandClaude Opus 4.8 66c99c5499 Add frame-aware locate for cross-origin iframe steps

Selectors were only resolved against the top document, so steps targeting
the Lucid WooCommerce checkout (rendered in a lucidtrading.com iframe under
the dash.lucidtrading.com app) never matched — e.g. input#coupon_code_field.

Add an optional `frame` on click/type/waitFor naming the <iframe> element.
The extension measures the iframe in the top frame (pageFrameOffset), finds
the element across child frames (pageLocate `relative` mode), and composes
the two into desktop coordinates; the Python side is unchanged since the
result keeps the same shape. Without `frame`, every path behaves as before.

Point the Lucid checkout steps at the frame and harden the coupon selectors
(the exact field id is still unconfirmed against the live iframe).

Extension 0.13.0, runner 0.19.0.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-09-02 13:22:10 -05:00

account-type-resolver.ts

Take firms from the master instead of defining them per machine

2026-08-31 22:17:23 -05:00

auto-trade.ts

Randomize daily targets: split big days into legs, bump min-days

2026-09-02 11:32:48 -05:00

automations.ts

Add frame-aware locate for cross-origin iframe steps

2026-09-02 13:22:10 -05:00

clients.ts

Take firms from the master instead of defining them per machine