Closed
Bug 14392
Opened 25 years ago
Closed 25 years ago
[PP] Web Page (URL) dialog: backspace does not work
Categories
(Core :: DOM: Editor, defect, P1)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: fenella, Assigned: akkzilla)
References
Details
Linux (1999-09-20-08 M11)
Win_nt 4.0 (1999-09-20-13)
Mac (1999-09-20-12 M11)
Steps:
1. Open Compose window
2. Compose a message. From the File menu, select Attach|Web page
3. Web page dialog comes up, enter url: http://home.netscape.com
4. Press the Back Space key
Actual result: Cursor goes forward
Expected result: Cursor should go backward and clear the text
This does not occur on Win_nt 4.0
On Mac: when pressing the Back Space key, cursor does not move. It does not
go backward or forward.
Since Mac has a different result, please let me know if I need to open a
separate bug.
Updated•25 years ago
|
Assignee: phil → buster
Comment 1•25 years ago
|
||
Sounds like an editor problem
Same build
The New Messenger Account Wizar: The Identity input area has the back space
problem as well.
The Mac bug with backspace is covered under
http://bugzilla.mozilla.org/show_bug.cgi?id=14493.
Updated•25 years ago
|
Assignee: buster → akkana
Component: Back End → Editor
Priority: P3 → P1
Product: MailNews → Browser
Target Milestone: M11
Comment 4•25 years ago
|
||
reassign to akkana. Akkana this sounds like a duplicate of 14347 though the
behavior described in this report is slightly different.
Updated•25 years ago
|
OS: All → Linux
Hardware: All → PC
Summary: Web Page (URL) dialog: back space does not work → [PP] Web Page (URL) dialog: backspace does not work
Comment 5•25 years ago
|
||
Since Windows doesn't seem to have this problem and Mac bug is #14493, I am
designating this as a [PP] bug for Linux.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
Fixed yesterday. Part of the continuing key event spec war.
Linux (1999-09-22-08 M11)
Win_nt 4.9 (1999-09-22-09 M11)
This problem is fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•