Closed Bug 354618 Opened 18 years ago Closed 8 years ago

Document the nsIFind::wordBreaker property as unused/unimplemented

Categories

(Core Graveyard :: Embedding: APIs, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: tom, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060921 Ubuntu/dapper-security Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060921 Ubuntu/dapper-security Firefox/1.5.0.7

Until #14871 is fixed, the nsFind::wordBreaker property should be documented as "unused". I wasted a lot of time attempting to implement the nsIWordBreaker interface only to discover that nsFind does not make any use of mWordBreaker.

When a working patch for #14871 is applied, this message can be removed.

Reproducible: Always

Steps to Reproduce:
1. Implement nsIWordBreaker
2. var wordBreaker = Components.classes["@domain.org/mywordbreaker;1"].createInstance().QueryInterface(nsIWordBreaker);
3. var finder = Components.classes["@mozilla.org/embedcomp/rangefind;1"].createInstance().QueryInterface(Components.interfaces.nsIFind);
4. finder.wordBreaker = myWordBreaker;
5. finder.Find(...)

Actual Results:  
finder.Find acts as if the wordBreaker property were never set (indeed, the code seems to suggest it's not used outside of the property setter/getter)

Expected Results:  
finder.Find should treat the wordbreaker as expected.

https://bugzilla.mozilla.org/show_bug.cgi?id=14871
Depends on: 14871
No longer depends on: 14871
Depends on: 14871
This bug still seems to exist. Marking NEW and moving to more appropriate component.
Status: UNCONFIRMED → NEW
Component: XPCOM → Embedding: APIs
Ever confirmed: true
OS: Linux → All
QA Contact: xpcom → apis
Hardware: x86 → All
Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.