Closed
Bug 213730
Opened 21 years ago
Closed 20 years ago
Replace asterisks rendered in INPUT type PASSWORD fields with IE6 style dots/bullets
Categories
(Core :: DOM: Editor, enhancement)
Core
DOM: Editor
Tracking
()
Future
People
(Reporter: galio, Assigned: Brade)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) it'll be good to replace the * signs for passwords with the dots used by m$ie 6. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•21 years ago
|
||
It's really not helpful to file a bug using a Netscape version and then file it Firebird specific when this is not Firebird specific. Resummarizing. Similar Mac-specific variant of this RFE: bug 97811. Moving to same Browser component as 97811.
Assignee: blakeross → jfrancis
Status: UNCONFIRMED → NEW
Component: General → Editor: Core
Depends on: 97811
Ever confirmed: true
Product: Firebird → Browser
QA Contact: asa → sairuh
Summary: replace *** with dots → Replace asterisks rendered in INPUT type PASSWORD fields with IE6 style dots/bullets
Version: unspecified → Trunk
Assignee | ||
Comment 2•21 years ago
|
||
What is the character? This is trivial to do if it's i18n-friendly. -->brade
Assignee: mozeditor → brade
Assignee | ||
Comment 3•21 years ago
|
||
need more information; without that I need to future
Target Milestone: --- → Future
Comment 4•20 years ago
|
||
This should be pretty easy (this is already the default list item style). It uses bullet (• - &8226;; • is supported on all Mozilla versions properly). :It doesn't look like the CSS specifications allow for input data display types.
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Updated•20 years ago
|
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Assignee | ||
Comment 6•20 years ago
|
||
duplicating bug and removing dependency I don't think the • idea will work because that maps to u2022 which is too small. I think we'd have to pair up that with an increased font size or something to get it to look right. Regardless, we should move the conversation to bug 97811. *** This bug has been marked as a duplicate of 97811 ***
You need to log in
before you can comment on or make changes to this bug.
Description
•