Closed
Bug 156924
Opened 23 years ago
Closed 18 years ago
Tab characters don't always align in compose window
Categories
(Core :: DOM: Editor, defect, P4)
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: jpybug, Unassigned)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1a) Gecko/20020611
BuildID: 2002061104
In the plaintext editor with fixed width font, tab characters only position the
carat correctly on a line when there is non-whitespace following the tab. If
the tabs are at the end of a line, they will position the carat short of the tab
stop. If a non-whitespace character is typed at the end of the line, the tabs
will expand to their proper width.
This is mostly an inconvenience when trying to build a table in the plaintext
editor.
Reproducible: Always
Steps to Reproduce:
1. Open a mail composition window.
2. Type a couple of tabs in the message body
3. Notice that the carat doesn't move the same distance each time
4. Type a alpha character.
5. Notice that the carat jumps forward to position the character at the
appropriate tab stop
Actual Results: The carat doesn't position itself on a tab stop until a
non-whitespace chacter is typed after the tab.
Expected Results: The carat should always align on the next tab stop when a tab
character is inserted.
Comment 2•23 years ago
|
||
reassign to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: esther → sujay
Updated•23 years ago
|
Priority: -- → P4
Target Milestone: --- → Future
Updated•18 years ago
|
QA Contact: sujay → editor
Updated•18 years ago
|
Assignee: kinmoz → nobody
Reporter | ||
Comment 3•18 years ago
|
||
I'm surprised that this bug is still open. I believe it was fixed when the similar bug 58712 was fixed back in 2002.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•