pj 970dc9a6f5 docs(hierarchy): the package doc states the match rules the code implements ...

id: was documented as a substring match and is exact-or-suffix-after-":id/", so
id:Button does not match com.x:id/saveButton; desc: is exact-or-prefix-before
", ". Bounds was declared inclusive while Width returns Right - Left, putting
every width, height and centre off by one against its own stated semantics. All
three producers emit exclusive right and bottom, so the code was right and the
comment was the only wrong copy. A test pins the arithmetic, including the
abutting and one-pixel cases the two conventions disagree on.

Also corrects which backend emits which bounds format: the paired form is what
both device backends send, the flat one is chrome and the stub.

2026-08-22 21:20:27 +05:30

..

hierarchy_test.go

docs(hierarchy): the package doc states the match rules the code implements

2026-08-22 21:20:27 +05:30

hierarchy.go

docs(hierarchy): the package doc states the match rules the code implements

2026-08-22 21:20:27 +05:30

selector_keys_test.go

record what the model picker did, and make both policies see the same actions (#74)

2026-08-19 11:07:49 +05:30