1705060 - UX review for new pdf signature infobar

Status: RESOLVED FIXED

(Firefox :: PDF Viewer, defect)

Description

[Romain Testard [:RT]]

Bug 854315 landed with ability to show pdf signatures that were previously hidden.
PDF documents with signatures will now always display a new inforbar (can be tested on latest nightly with https://bug854315.bmoattachments.org/attachment.cgi?id=728861) that informs the users that the digital signature is not validated with a button allowing users to open with a different viewer - Edge in most cases for Windows users.

Here are some concerns I'd like UX help with:

• Most users will follow OS defaults and Edge does not support digital signature validation either (and also does not inform users that they do not support it) - essentially we send users to another browser where they think a feature is supported that is not supported in Firefox, although it's not true
• In general I feel like most users won't understand what the infobar means. Competing browsers (Chrome and Edge) also don't support digital signature validation but don't warn users - I'd recommend not showing a notification here to avoid confusing users on something that is not critical to their security (users now see a signature in a PDF document but nothing in the UI signals that the piece of previously hidden text has any form of official warranty)

Comment 1

[Romain Testard [:RT]]

Betsy, can you please share your thoughts here on the infobar implementation?

Comment 2

[Betsy Mikel [:betsymi]]

UX recommends not showing this infobar notification unless there is a significant security reason to include it. This aligns with the same decision UX and PM made regarding other PDF fall-back features. This PDF document might not be displayed correctly. and This PDF document contains forms. The filling of form fields is not supported. should have also been removed.

Comment 3

[Romain Testard [:RT]]

Thanks Betsy
ccing mkaply for information
Calixte, can you please advise if we're fine with removing the infobar? In any case can you please confirm that the current implementation will not get to Beta?