Open Bug 82055 Opened 23 years ago Updated 4 years ago

Cannot select double-byte chars using mouse in Rename Profile

Categories

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

x86
Windows ME
defect

Tracking

()

Future

People

(Reporter: jonrubin, Unassigned)

References

Details

(Keywords: intl, Whiteboard: [select])

Found on WinMe-Ja using 2001052111 Trunk Build. Steps: 1) In Profile Manager, choose an existing double-byte profile and click "Rename Profile" 2) Try to select the characters using the mouse; some, or none, of the characters will be selectable. It is possible to backspace and delete characters. Note: This problem didn't occur for all characters. For a testcase, try "tarou" (‘¾˜Y). In my test, I could highlight the second character, but not the first.
Changing component to Internationalization.
Component: Profile Manager FrontEnd → Internationalization
Keywords: intl
QA Contact: gbush → jonrubin
there's a generic bug for not being able to select the first character of an edit box...
Yup, and that's bug 80028.
The behavior of this bug was very sporadic. At first, I could not select any characters for a profile that contained Japanese characters, but I could select all letters in profiles containing only single byte chars. Then, as I re-tested, I could select all chars in all profiles (regardless of single or double byte), except for one of the profiles--the "tarou" profile that I explained in my note. For this profile, the behavior was consistent: I could select the second Kanji character, but not the first.
Blocks: 79151
nav triage team: This sounds like xptoolkit. Changing component to xptoolkit and reassigning to default owner and qa contact
Assignee: ben → trudelle
No longer blocks: 79151
Component: Internationalization → XP Toolkit/Widgets
QA Contact: jonrubin → aegis
Blocks: 79151
edit boxes are editor's area
Assignee: trudelle → beppe
Component: XP Toolkit/Widgets → Editor
QA Contact: aegis → sujay
mjudge
Assignee: beppe → mjudge
Priority: -- → P3
Whiteboard: [select]
Target Milestone: --- → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
retargeting
Target Milestone: mozilla1.0.1 → Future
QA Contact: sujay → editor
Assignee: mjudge → nobody

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), 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.