Ticket #6324 (closed defect: wontfix)

Opened 8 months ago

Last modified 5 months ago

TextArea: can only enter a single char on last line (Safari 3.1/mac/romaji IME)

Reported by: bill Owned by: bill
Priority: high Milestone: 1.2
Component: Dijit Version: 1.0
Severity: normal Keywords:
Cc:

Description (last modified by bill) (diff)

  1. Load test_Textarea.html on safari 3.1/mac.
  2. Focus on "this is a very simple resizable text area"
  3. make sure caret is at end of line, and hit return
  4. type "a" key multiple times. only one "a" appears

I feel like there was another bug open about this that was fixed (but not against safari 3.1), but I can't find it now.

Note that it works correctly on Safari 3.1/windows.

Attachments

6324_testcase.html (1.1 kB) - added by bill 8 months ago.
test case showing bug (using plain markup)
6324_workaround.html (1.2 kB) - added by bill 8 months ago.
test case showing possible workaround

Change History

Changed 8 months ago by bill

  • description modified (diff)
  • summary changed from TextArea: can only enter a single char on last line (Safari 3.1) to TextArea: can only enter a single char on last line (Safari 3.1/mac)

Changed 8 months ago by bill

test case showing bug (using plain markup)

Changed 8 months ago by bill

test case showing possible workaround

Changed 8 months ago by doughays

  • owner set to bill
  • description modified (diff)

Changed 8 months ago by bill

Note that apparently no one is seeing this bug besides me.

The solution I have to remove the <fieldset> seems like it works but of course any such change is scary.

Changed 5 months ago by bill

  • description modified (diff)

Changed 5 months ago by bill

  • status changed from new to closed
  • resolution set to wontfix
  • summary changed from TextArea: can only enter a single char on last line (Safari 3.1/mac) to TextArea: can only enter a single char on last line (Safari 3.1/mac/romaji IME)

I figured out this only happens for me. I'm running MacOS English but with the Japanese IME. When it's set to "romaji" rather than "U.S." the problem happens. "Romaji" and "U.S." are essentially the same setting (except that the former causes this bug :-( ).

I just asked someone to try a Japanese OS and this doesn't reproduce for them either; I guess it's a really esoteric bug that we shouldn't bother fixing.

Note: See TracTickets for help on using tickets.