Open Bug 143950 Opened 22 years ago Updated 3 years ago

didn't add "space" char at the end of line

Categories

(Core :: DOM: Editor, defect, P5)

x86
Windows XP
defect

Tracking

()

Future

People

(Reporter: anton.krugliakov, Unassigned)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2)
Gecko/20020510
BuildID:    2002051006

didn't add "space" char at the end of line in <textarea> tag


Reproducible: Always
Steps to Reproduce:
1.Select quick-post fiels at the bottom of page
2.input chars to fill line to right edge
3.try to input space chars

Actual Results:  space chars didn't appear

Expected Results:  add space chars
-> Editor:Core and confirming with win2k build 20020511..
Assignee: Matti → kin
Status: UNCONFIRMED → NEW
Component: Browser-General → Editor: Core
Ever confirmed: true
QA Contact: imajes-qa → sujay
Where did you expect the space to appear exactly?  We used to show them on the
next line (wrap between spaces) and that looks ugly.  So now we do not show
spaces that are at the end of a line, we just wrap on them.
Look in IE ( i think it works great with edit field )
It add spaces at the end of line as normal chars.
The IE way makes the textfield keep scrolling right and left as I type if I type
two-space sentence separators at the boundary...  See bug 19265 for the
discussion on this feature.
Depends on: 164459
*** Bug 189700 has been marked as a duplicate of this bug. ***
I think the choice should belong to the final user...this is what I call
customization then...by the way, this is not a standart behaviour not to write
this space...so I think a browser that claims compliancy to standards shouldn't
behave this way

Moreover, for certain usage, it's very useful to have the caracter
written...like when posting on forum, when doing ASCII arts or trying to have a
special layout, like reproducting a table layout in ASCII (most of forum forms
don't take into account the tab space)

so for al these reasons, the choice should be left to final user
Priority: -- → P3
Target Milestone: --- → Future
*** Bug 249296 has been marked as a duplicate of this bug. ***
I posted bug number 249296.  I don't see how this can be correct.  How do you
know that you typed a space?  I end up typing several spaces before I realize
that they just aren't showing up.

You've read bug 19265, right?  If not, please do.
I have now, and I guess I'm still lost.  Has this bug been fixed?  I seems odd
that you wouldn't want to show a space when typed? 
This bug is really just a special case of bug 87314.
QA Contact: sujay → editor
Assignee: kinmoz → nobody

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.