Closed
Bug 162982
Opened 23 years ago
Closed 22 years ago
Lacking default tooltip impl for embeddors
Categories
(Core Graveyard :: Embedding: APIs, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: aaronlev, Assigned: adamlock)
Details
Embeddors have to impl nsITooltipListener, we don't provide a default impl.
I think this is unfriendly and creating extra work for most embeddors; we should
let them override the impl, but not force them to do something we should provide.
The problem with providing a default implementation is that it is impossible to
do in a cross platform manner. It might be possible to work on a Win32 version.
Reporter | ||
Comment 2•23 years ago
|
||
What makes it impossible to do it XP?
Geecko renders everything else XP, why not tooltips?
If the embedder wants an XP toolkit they should load some chrome into their
browser object with the appropriate tooltip js event handler. This can be done
right now.
The nsIToolTipListener is for the benefit of embedders who wish to implement a
tooltip behaviour in C++. Perhaps we could provide an XP version of this, but it
might be tricky considering the different paths that a tooltip would be invoked
from via chrome and via our listener class.
Updated•23 years ago
|
QA Contact: mdunn → ashishbhatt
Marking WONTFIX.
Embedders now have a sample tooltip implementation in mfcembed to reference.
http://lxr.mozilla.org/seamonkey/source/embedding/tests/mfcembed/BrowserToolTip.h
http://lxr.mozilla.org/seamonkey/source/embedding/tests/mfcembed/BrowserToolTip.cpp
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 5•18 years ago
|
||
> If the embedder wants an XP toolkit they should load some chrome into their
> browser object with the appropriate tooltip js event handler. This can be done
> right now.
Can you give a hint how to load some chrome into a nsIWebBrowser, please?
Sure, I can call nsIWebNavigation.loadURI() with a chrome uri, but I also need to load a webpage.
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•