Bugzilla

STR:
1a. Visit `file:///` (or any file URI)
...or:
1b: Open a new tab.

2. Ctrl+F to find-in-page, and type something (e.g. `aaa`)

3. Ctrl+L to focus the URL bar, type example.org, and hit enter.

ACTUAL RESULTS:
The find bar remains open, but its contents are cleared.

EXPECTED RESULTS:
The find bar's contents should not have been cleared (since it's still open and I'm still using it).


I *think* this clearing is caused by a process-switch -- in this case, the switch from the `about` process or the `file://` process to one of your other regular content processes.  But as fission progresses and processes-per-origin get more numerous/granular, this will happen when you navigate between between any pair of pages whose origins differ, I imagine.

Note: If I perform this STR with a navigation from e.g. https://example.org to https://bugzilla.mozilla.org, then I get EXPECTED RESULTS with default settings vs. ACTUAL RESULTS if I enable `fission.autostart`; so that increases my confidence that this is a fission (process-switching) bug.)

STR:
1a. Visit `file:///` (or any file URI)
...or:
1b: Open a new tab.
2. Ctrl+F to find-in-page, and type something (e.g. `aaa`)
3. Ctrl+L to focus the URL bar, type example.org, and hit enter.

ACTUAL RESULTS:
The find bar remains open, but its contents are cleared.

EXPECTED RESULTS:
The find bar's contents should not have been cleared (since it's still open and I'm still using it).


I *think* this clearing is caused by a process-switch -- in this case, the switch from the `about` process or the `file://` process to one of your other regular content processes.  But as fission progresses and processes-per-origin get more numerous/granular, this will happen when you navigate between between any pair of pages whose origins differ, I imagine.

Note: If I perform this STR with a navigation from e.g. https://example.org to https://bugzilla.mozilla.org, then I get EXPECTED RESULTS with default settings vs. ACTUAL RESULTS if I enable `fission.autostart`; so that increases my confidence that this is a fission (process-switching) bug.)

STR:
1a. Visit `file:///` (or any file URI)
...or:
1b: Open a new tab.
2. Ctrl+F to find-in-page, and type something (e.g. `aaa`)
3. Ctrl+L to focus the URL bar, type example.org, and hit enter.

ACTUAL RESULTS:
The find bar remains open, but its contents are cleared.

EXPECTED RESULTS:
The find bar's contents should not have been cleared (since it's still open and I'm still using it).


I *think* this clearing is caused by a process-switch -- in this case, the switch from the dedicated `file://` process or the `about:newtab` process to one of your other regular content processes.  But as fission progresses and processes-per-origin get more numerous/granular, this will happen when you navigate between between any pair of pages whose origins differ, I imagine.

Note: If I perform this STR with a navigation from e.g. https://example.org to https://bugzilla.mozilla.org, then I get EXPECTED RESULTS with default settings vs. ACTUAL RESULTS if I enable `fission.autostart`; so that increases my confidence that this is a fission (process-switching) bug.)

STR:
1a. Visit `file:///` (or any file URI)
...or:
1b: Open a new tab.
2. Ctrl+F to find-in-page, and type something (e.g. `aaa`)
3. Ctrl+L to focus the URL bar, type example.org, and hit enter.

ACTUAL RESULTS:
The find bar remains open, but its contents are cleared.

EXPECTED RESULTS:
The find bar's contents should not have been cleared (since it's still open and I'm still using it).


I *think* this clearing is caused by a process-switch -- in this case, the switch from the dedicated `file://` process or the `about:newtab` process to one of your other regular content processes.  But as fission progresses and processes-per-origin get more numerous/granular, this will happen when you navigate between between any pair of pages whose origins differ, I imagine.

Note: If I perform a variant of my STR, with a navigation from e.g. https://example.org to https://bugzilla.mozilla.org (with findbar open with some contents before I navigate), then I get EXPECTED RESULTS with default settings vs. ACTUAL RESULTS if I enable `fission.autostart`; so that increases my confidence that this is a fission (process-switching) bug.)