canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
Community:SummerOfCode06: Difference between revisions
Jump to navigation
Jump to search
→Core Browser Engine and Toolkit Development: selection APIs
(remove plugin item added by Rmarxer (who's that?) - what we really want is out-of-process, not multithreaded, multithreaded really isn't useful progress towards that, and out-of-process is too mch wrk) |
(→Core Browser Engine and Toolkit Development: selection APIs) |
||
| Line 133: | Line 133: | ||
| valign="top" |Reporter: [[User:richwklein|richwklein]] | | valign="top" |Reporter: [[User:richwklein|richwklein]] | ||
| valign="top" |Submitted: 8:26, 21 April 2006 (CST) | | valign="top" |Submitted: 8:26, 21 April 2006 (CST) | ||
|- | |||
| valign="top" | | |||
| valign="top" |Enhance selection APIs | |||
| valign="top" |Enhance the selection APIs so that they can provide the features needed for both existing find-in-page use (without modifying the DOM) and for highlighting of all occurrences. Start by reorganizing the selection code based on what requirements it really needs to meet (which include handling of text selection in the page and in form controls, IME, spellcheck, and other things) plus the ability to [https://bugzilla.mozilla.org/show_bug.cgi?id=256773 select multiple ranges]. (And maybe do some [https://bugzilla.mozilla.org/show_bug.cgi?id=298715 other cleanup] as part of that learning process.) Then extend CSS and DOM APIs to provide a clean API for what find-in-page needs, and fix find-in-page to use those APIs. | |||
| valign="top" |Reporter: [[User:Dbaron|David Baron]] | |||
| valign="top" | | |||
|- | |- | ||
|} | |} | ||