Closed
Bug 2039838
Opened 3 months ago
Closed 1 month ago
Client supports watermarking by domain
Categories
(Enterprise Products :: Firefox, enhancement, P1)
Tracking
(firefox155 verified, firefox156 verified)
VERIFIED
FIXED
MVP
People
(Reporter: bsmth, Assigned: fiji)
References
(Blocks 1 open bug)
Details
(Whiteboard: [size=2.5])
User Story
As an enterprise admin, I want clients to apply watermarking according to a configured policy, so that specific domains display the required watermark when the policy conditions are met. Acceptance criteria: - The client supports a watermarking policy. - When a domain is loaded matching the policy, the client applies a watermark overlay to the web content. The watermark text: - is displayed repeatedly across the page content. - is composed of a string defined in the Watermarking policy, otherwise is the user SSO ID. - uses a color defined in the Watermarking policy. - The watermark is removed when the user navigates away from the specified domain.
Attachments
(2 files)
Screenshot 2026-07-23 at 12.04.01.png
No description provided.
|
||
Updated•2 months ago
|
Severity: -- → S1
tracking-firefox152:
--- → ?
tracking-firefox152:
? → ---
tracking-firefox153:
--- → ?
tracking-firefox153:
? → ---
Whiteboard: [size=2.5]
|
||
Updated•2 months ago
|
Assignee: nobody → fmerz
|
||
Comment 1•1 month ago
|
||
|
|
||
Comment 2•1 month ago
|
||
Authored by https://github.com/fiji-flo
https://github.com/mozilla/enterprise-firefox/commit/ebf3b4383e85055e7df21091ba4bba8c140fce24
[enterprise-main] Bug 2039838 - Add Watermark policy
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
|
||
Comment 3•1 month ago
|
||
Please find in this Figjam board design and logic for the Watermarking policy. It shows how the various parameters of the policy can alter what the client sees (or is made aware of):
https://www.figma.com/board/fmCVdliqQmr7dKCFNkxmKX/Watermarking?node-id=0-1&t=NQRtHg7FWuEzuxaJ-1
Thoughts and feedback welcome!
|
||
Comment 4•15 days ago
|
||
The watermarking policy is available in the console and is configurable as JSON.
You need to log in
before you can comment on or make changes to this bug.
Description
•