Closed Bug 143387 Opened 22 years ago Closed 12 years ago

Tracking bug for Embedding API Reference

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jeev13, Unassigned)

References

()

Details

Please file any questions, additions, errors, etc re: this document here.  

Thanks.
Status: NEW → ASSIGNED
QA Contact: imajes → rudman
can you confirm the url for this document? if it's what i am thinking it is, i
am working on it already...
The URL will be added when the APIs are posted - probably by Friday, the 17th.

Thanks for the additional info, James.
Added URL
Nitpicks:

In the nsIInputStream list of methods
(http://mozilla.org/projects/embedding/embedapiref/embeddingapiTOC.html), "clos"
should be "close"

In nsIProfile
(http://mozilla.org/projects/embedding/embedapiref/embedapi56.html#1025700)
SHUTDOWN_CLEANSE is bigger than SHUTDOWN_PERSIST.

Thanks for the awesome ref!
I'm wondering if you could change the bgcolor #0000099 to something else because
it's exactly the same as the text selection color. In other words it's not
possible to see what you're selecting if you're over a block with that color. A
tad annoying.

Also putting the layout stuff in a style sheet would ease updating, the
documents would become smaller and less error prone blah blah..
"clos" -> "close", will fix the size problem today.

I'm working on moving to a .css version, should be available in the next couple
of weeks.  That should make the underlying code much easier to look at.  The
disappearing text in table thing doesn't happen on my machine.  What platform
are you using?  I can certainly adjust the shade of blue if you think it would
help.  The blue itself is part of the old style recommendations.
nsIProfile font size issue fixed

Thanks for all the good feedback, everyone
I've added the Necko interfaces, nsIFile/LocalFile, and nsIURIContentListener,
which, I think, brings the ref up to Moz 1.0 freeze levels.  If I've missed
anything, please let me know.
I've added interfaces frozen between 1.0 and 1.4.
Depends on: 161912
Depends on: 150448
The frozen interface at 
http://www.mozilla.org/projects/embedding/embedapiref/embedapi55.html#1150910
specifies nsIIOService::offline as an attribute available for setting offline mode, and the documentation does not mention SetOffline or GetOffline.

When I attempt to use the offline attribute, I get an error message stating there is no member named 'offline'.

Eventhough SetOffLine is not documented as part of the frozon interface, it does work.

Could you please clarify if 'offline' is part of the frozen interface, and please consider updating the documentation on the frozen interface to include SetOffLine and GetOffLine.

Thank You,
Don.
I wonder if it's possible to change de print windows itself. eg: change the shape of the pages, or enter a new text, somewhere on the window. 

thanks
Product: mozilla.org → Websites
Assignee: jeev → nobody
Status: ASSIGNED → NEW
Component: Mozilla Developer → www.mozilla.org
Product: Documentation → mozilla.org
QA Contact: rudman → www-mozilla-org
Version: unspecified → other
Sheppy, should this Embedding API Reference content on www.mozilla.org be redirected to

http://developer.mozilla.org/En/Gecko_Embedding_API_Reference
In theory, except a lot of that material doesn't look like it's migrated yet.
Could you please mention the necesary include file and library file when describing a function/interface in the embedding API ?
I have found (using XULRunner compiled from mozilla-1.9.1 sources for Firefox) that embedder-provided nsWebBrowserChrome should also implement nsIInterfaceRequestor and nsIWeakReference (other than nsIEmbeddingSiteWindow) in order used by the runtime. Could this note be added on the page ?
To follow up on this bug, archiving legacy content is now a requirement for being able to move forward with the mozilla.org/.com merge.

If there is no plan to manually migrate this content in the short term, we will go ahead with moving this content off of www.mozilla.org and putting it someplace where it can decide what to do with it on your own schedule.  That may be either the www-archive.mozilla.org site or an archive section of MDN.
I personally have not been maintaining this doc since Netscape folded in 2003.  So I'm not sure who should have ownership of it going forward.
If no one currently owns this then archiving it makes sense.  This will let people know the content is not up to date and will leave the content in a place that is available for someone to update and migrate back to an appropriate place later.  I'll archive this soon unless there are objections.
I'm closing this bug as this no longer exists on www.mozilla.org and has all been moved to www-archive.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.