309476 - Text selection display bug in HTML form textarea elements

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[David]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

Copied text from a webpage genrates square characters in a HTML textarea form
element. Selecting the text generates the first image selection bug and pressing
a key like "Home" generates the second image linked below that gives an unselect
display bug.

Complementary Image : http://scriptsdb.org/sshot/2884_1127312943.png

Reproducible: Always

Steps to Reproduce:
1. go to http://scriptsdb.org/forum.php?fid=3&thread=0&reply=40520
2. Copy the text part starting with on ^*:notice up to the ending code bracket }
3. Copy the contents to another HTML textarea form like in the bugtracking form
4. See some small square chars appear and select the whole text to see selection bug
5. unselect to see remaining unselection bug

Actual Results:  
This is the copied text, don't know how it will render once sent through the form.

on ^*:notice:*:?: {
if (%exnotice == $null) { %exnotice = $c(notice) $+ (..notice..) }
echo -albf $chan $timestamp $c(notice) $+ 8 $+ %exnotice $nick $+ : $c(notice)
$1- | haltdef
}

Expected Results:  
Expected to have the original text copied properly and no display bug on
selection/unselection of text in textarea element.

Windows 2k SP4
FireFox 1.5 Beta 1
Office 2003 Green Theme

about:buildconfig

Build platform
target
i586-pc-msvc

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -Gy -Fd$(PDBFILE)

Configure arguments
--enable-application=browser --enable-update-channel=beta --enable-optimize
--disable-debug --disable-tests --enable-static --disable-shared
--enable-official-branding --enable-svg --enable-canvas --enable-update-packaging

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

The source page uses a windows-1252 character set and contains some wired UTF-8 characters. So the problem is still there. The browser behaves correctly. Marking as invalid again.