(In reply to Edgar Chen [:edgar] (Parental leave until Oct. 09.) from comment #17) > (In reply to Hsin-Yi Tsai (she/her) (REO Fx 129) [:hsinyi] from comment #16) > > It may depend on the response or how quickly we will get from the Outlook folks; however I wonder if there is another workaround in addition to temporarily disabling clipboard.read() only for outlook. While the copy/paste functionality isn't necessarily broken, breaking the user work flow is a significant regression imo. > > I filed bug 1906285 to support disabling `clipboard.read()` from domain list. https://bugzilla.mozilla.org/show_bug.cgi?id=1906614 said the issue started with Fx 124, while I was confused with the version, as clipboard.readText() was shipped in Fx 125. But since we implemented the same privacy model with a context menu for .readText(), we should keep .readText() in mind.
Bug 1815733 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Edgar Chen [:edgar] (Parental leave until Oct. 09.) from comment #17) > (In reply to Hsin-Yi Tsai (she/her) (REO Fx 129) [:hsinyi] from comment #16) > > It may depend on the response or how quickly we will get from the Outlook folks; however I wonder if there is another workaround in addition to temporarily disabling clipboard.read() only for outlook. While the copy/paste functionality isn't necessarily broken, breaking the user work flow is a significant regression imo. > > I filed bug 1906285 to support disabling `clipboard.read()` from domain list. Bug 1906614 said the issue started with Fx 124, while I was confused with the version, as clipboard.readText() was shipped in Fx 125. But since we implemented the same privacy model with a context menu for .readText(), we should keep .readText() in mind.
(In reply to Edgar Chen [:edgar] (Parental leave until Oct. 09.) from comment #17) > (In reply to Hsin-Yi Tsai (she/her) (REO Fx 129) [:hsinyi] from comment #16) > > It may depend on the response or how quickly we will get from the Outlook folks; however I wonder if there is another workaround in addition to temporarily disabling clipboard.read() only for outlook. While the copy/paste functionality isn't necessarily broken, breaking the user work flow is a significant regression imo. > > I filed bug 1906285 to support disabling `clipboard.read()` from domain list. Bug 1906614 said the issue started with Fx 124, while I was confused with the version, as clipboard.readText() was shipped in Fx 125. But since we implemented the same privacy model with a context menu for .readText(), we should also keep .readText() in mind, in addition to .read().