Privacy: secure rectangles and view-tree nodes inside a Modal use the Modal's own origin by krassx · Pull Request #48 · bugsee/bugsee-react-native

fix(android): serve each React surface's secure rects by its own origin

krassx

committed

35d6794

fix(ios): keep per-surface secure lanes with their own origin

krassx

committed

76eeb56

fix(privacy): publish <BugseeSecure> and managed nodes on their own surface

krassx

committed

3d58f09

test(e2e): cover <BugseeSecure> inside a <Modal> on both surfaces

krassx

committed

ab84802

fix(privacy): place each Modal by its own root, keyed off the fiber tree

krassx

committed

99ae355

test(e2e): find each secure view by its colour, and add the discriminating Modals

krassx

committed

7895840

test(e2e): an opaque pageSheet hides the main secure view

krassx

committed

020b682

test(secure): expect the error's name in BugseeSecure's warning

krassx

committed

5877a03

fix(privacy): bound and clamp what the secure store serves, and fail closed on every lane

krassx

committed

9ec0e5e

test(e2e): check the Modal's secure view in every video frame too

krassx

committed

b349408

fix(privacy): drop a JS runtime's Modal surfaces when it goes away

krassx

committed

53023ab

chore(android): log at debug what a JS runtime's claim and release drop

krassx

committed

be4bf5e

fix(privacy,android): ignore secure-store writes from a runtime whose claim is stale

krassx

committed

756d531

fix(privacy,ios): ignore secure-store writes from a runtime whose claim is stale

krassx

committed

3cbce1b

fix(ios): find a Modal host by class and React tag, not viewWithTag:

krassx

committed

f0a421b

fix(android): a runtime claim empties the main surface's rectangles

krassx

committed

e3463b7

fix(ios): a runtime claim empties the main surface's rectangles

krassx

committed

86a0b75

fix(privacy,ios): place a Modal lane by the current runtime's own host

krassx

committed

311de7c

fix(privacy,ios): a named Modal host that is not found yet fails closed

krassx

committed

a72596f

Navigation Menu

Repository navigation

Privacy: secure rectangles and view-tree nodes inside a Modal use the Modal's own origin - #48

Privacy: secure rectangles and view-tree nodes inside a Modal use the Modal's own origin#48
krassx merged 19 commits into
mainfrom
fix/modal-secure-origin

Commits on Oct 5, 2026

fix(android): serve each React surface's secure rects by its own origin

fix(ios): keep per-surface secure lanes with their own origin

fix(privacy): publish <BugseeSecure> and managed nodes on their own surface

test(e2e): cover <BugseeSecure> inside a <Modal> on both surfaces

fix(privacy): place each Modal by its own root, keyed off the fiber tree

test(e2e): find each secure view by its colour, and add the discriminating Modals

test(e2e): an opaque pageSheet hides the main secure view

test(secure): expect the error's name in BugseeSecure's warning

fix(privacy): bound and clamp what the secure store serves, and fail closed on every lane

test(e2e): check the Modal's secure view in every video frame too

fix(privacy): drop a JS runtime's Modal surfaces when it goes away

chore(android): log at debug what a JS runtime's claim and release drop

fix(privacy,android): ignore secure-store writes from a runtime whose claim is stale

fix(privacy,ios): ignore secure-store writes from a runtime whose claim is stale

fix(ios): find a Modal host by class and React tag, not viewWithTag:

fix(android): a runtime claim empties the main surface's rectangles

fix(ios): a runtime claim empties the main surface's rectangles

fix(privacy,ios): place a Modal lane by the current runtime's own host

fix(privacy,ios): a named Modal host that is not found yet fails closed