Closed
Bug 62099
Opened 24 years ago
Closed 24 years ago
The winEmbed sample needs to exercise more of the embedding API.
Categories
(Core Graveyard :: Embedding: APIs, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: adamlock, Assigned: adamlock)
Details
Attachments
(2 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review |
winEmbed is too limited for a proper smoketest of the embedding APIs. Improve
the interface so that more of the APIs can be tested.
Hi Doug, can you review the following attachment. Basically it makes winEmbed
behave more like a normal browser with go, stop, back, forward, address fields
+ a status bar?
I don't know what our sr= procedure should be for an embedding test app but if
you're happy with progress so far I can checkin.
Status: NEW → ASSIGNED
Comment 4•24 years ago
|
||
sr=rpotts
looks fine to me.
Thanks Rick, changes are checked in
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 7•24 years ago
|
||
Correction: Changing QA contact for the Embed API bugs to David Epstein.
QA Contact: mdunn → depstein
Comment 8•24 years ago
|
||
event methods called in WinEmbed.cpp. Browser and listener methods implemented
in WebBrowserChrome.cpp
Status: RESOLVED → VERIFIED
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
•