pj 7066b23a22 fix(web-runtime): answer clickable for an element reached through ax ...

The handle hardcoded true, so every text node and container a spec reached
through state.ax claimed to be a tap target while the enumeration and the
hierarchy dump both resolved it through the tappable selector.

The parity test now compares the handle against the enumeration element by
element in a real browser, which is where the three answers have to agree.

Claude-Session: https://claude.ai/code/session_01A5KmftdEJ49A9z5mF5ESrX

2026-08-15 13:45:30 +05:30

..

testdata

fix(chrome): name a web field by its hint, not its CSS class

2026-08-15 13:45:30 +05:30

driver_test.go

fix(chrome): name a web field by its hint, not its CSS class

2026-08-15 13:45:30 +05:30

driver.go

fix(chrome): name a web field by its hint, not its CSS class

2026-08-15 13:45:30 +05:30

fact_parity_test.go

fix(web-runtime): answer clickable for an element reached through ax

2026-08-15 13:45:30 +05:30

launch_test.go

fix ltl semantics and unify action enumeration (#71)

2026-08-12 18:06:04 +05:30

selector_parity_test.go

test(chrome): drive the live-page parity test through both selector forms

2026-08-13 00:41:23 +05:30

translate_test.go

fix(spec): match a merged label by its leading name on web too

2026-08-13 00:41:23 +05:30

translate.go

fix(spec): match a merged label by its leading name on web too

2026-08-13 00:41:23 +05:30