Closed
Bug 39646
Opened 24 years ago
Closed 24 years ago
insertion of anchor should do the right thing when typing
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
M18
People
(Reporter: Brade, Assigned: cmanske)
Details
(Whiteboard: [nsbeta3+])
When I am typing an anchor in the edit field, I am permitted to type spaces but then they are automatically converted. I think we should either not allow spaces to be typed or we should change the space to an underscore. Of course we may need to be careful with ime stuff here.
Assignee | ||
Comment 1•24 years ago
|
||
You mean convert a space to "_" as they are typing? Why don't you like the conversion after you finish?
Reporter | ||
Comment 2•24 years ago
|
||
Yes, I mean as a person types. I don't like the conversion after I'm done because it is hidden from the user (they don't know what character the space was converted to).
Assignee | ||
Comment 3•24 years ago
|
||
I guess we can do something like we do in "ForceInteger()" to replace as they type.
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Assignee | ||
Updated•24 years ago
|
Target Milestone: M17 → M19
Assignee | ||
Comment 4•24 years ago
|
||
Simple fix -- replace "bad" characters such as spaces to "_" as user types and remove the "(Spaces are not allowed)" string in the dialog.
Keywords: nsbeta3
Comment 5•24 years ago
|
||
setting to nsbeta3+ Charley, can you please add the level of priority -- thanks
Assignee | ||
Comment 6•24 years ago
|
||
Named anchor issues are now tracked in bug 47687 *** This bug has been marked as a duplicate of 47687 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•