Summary: | REGRESSION: New text fields should compute maxlength considering composed character sequences | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Adele Peterson <adele> | ||||
Component: | Forms | Assignee: | Darin Adler <darin> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | Keywords: | Regression | ||||
Priority: | P1 | ||||||
Version: | 420+ | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.4 | ||||||
Attachments: |
|
Description
Adele Peterson
2006-03-05 21:39:32 PST
Bumping to P1 since this causes a text field regression These are all text field regressions so they should all be P1. The API for this is in ICU, in <unicode/ubrk.h>. If we use a UBRK_CHARACTER iterator, then we can find characer boundaries. I think I'll tackle this. I've got the fix for this written; just need to write some layout tests. I also fixed a regression where changing maxlength would not immediately truncate the value that's already in the text field. Created attachment 7587 [details]
patch, including change log and a layout test
|