D
Don Y
Guest
On 8/16/2022 10:58 AM, whit3rd wrote:
No, I mean having two \"tabs\" of the same browser-based *application* running
in different browsers.
E.g., An application that automates preparation of a tax return. Tab 1 shows
my 1040 and tab 2 shows my schedule A. Changes to schedule A in tab 2 are
automatically reflected on the 1040 in tab 1.
Now, have tab 1 be in an Edge browser and tab 2 be in Firefox.
This is contrary to the security model the browser is supposed to
provide; tab 1 shouldn\'t be able to interact with tab 2 (except
via client-side storage/cookies). Being able to bridge the
protection domain that a different application imposes should
(presumably) be \"impossible\" -- except for super cookies?
On Tuesday, August 16, 2022 at 10:28:26 AM UTC-7, Don Y wrote:
[To be truly amusing, imagine opening two different browsers on the same
machine. Should they *ever* be permitted to \"co-operate\"?]
No need to imagine, I\'m doing it. The main cooperation required, is just that
I can drag an address from the browser that mangles the page, to the
icon in the dock of the other browser, and see if that helps. Often, it does.
Latest issue: light-grey font on white. Gotta cut-and-paste into a text editor
to see it, multiple browsers don\'t help. I certainly DO miss the old \'show source\'
feature, which allowed some disentanglements in the past.
No, I mean having two \"tabs\" of the same browser-based *application* running
in different browsers.
E.g., An application that automates preparation of a tax return. Tab 1 shows
my 1040 and tab 2 shows my schedule A. Changes to schedule A in tab 2 are
automatically reflected on the 1040 in tab 1.
Now, have tab 1 be in an Edge browser and tab 2 be in Firefox.
This is contrary to the security model the browser is supposed to
provide; tab 1 shouldn\'t be able to interact with tab 2 (except
via client-side storage/cookies). Being able to bridge the
protection domain that a different application imposes should
(presumably) be \"impossible\" -- except for super cookies?