Open Bug 201742 Opened 22 years ago Updated 2 years ago

make the cipher suite name in the page info -> security dialog selectable/copyable

Categories

(Firefox :: Page Info Window, enhancement)

enhancement

Tracking

()

People

(Reporter: craig, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 When you try to copy security data from page info, it's impossible, since it's impossible to even mark it. Reproducible: Always Steps to Reproduce: 1. go to any secure page 2. page info/security 3. try to mark any text for copying Actual Results: nothing Expected Results: Marked text and allowed me to copy it. When you come across a site running, say, low-grade security and want to report it to them, the easier approach would be to copy/paste the Mozilla report into email to them, especially since most first-line support people immediately ask "what exactly does your browser display?"
The security UI is maintained by the security folks. Over to them.
Assignee: db48x → ssaux
Status: UNCONFIRMED → NEW
Component: Page Info → Client Library
Ever confirmed: true
OS: Windows 98 → All
Product: Browser → PSM
QA Contact: pmac → bmartin
Hardware: PC → All
Version: Trunk → 2.4
Severity: normal → enhancement
Similar to bug 200621
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
Product: PSM → Core
QA Contact: bmartin → ui
Version: psm2.4 → 1.0 Branch
As far as I can tell, the only thing that isn't currently selectable (and thus copyable) is the cipher suite (note that if you use the network panel in the devtools, it is selectable). In any case, this would be a modification to the Page Info dialog, which as far as I know is maintained by Firefox folks.
Component: Security: UI → Page Info Window
Product: Core → Firefox
Summary: impossible to mark/copy security data → make the cipher suite name in the page info -> security dialog selectable/copyable
Version: 1.0 Branch → unspecified
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.