91161 - [mfcEmbed] MFCEMBED's file URL's don't bring up directories

Status: RESOLVED WONTFIX

(Core Graveyard :: Embedding: APIs, defect)

Description

[Aaron Leventhal]

This is smoketest item EM 7
from http://www.mozilla.org/quality/smoketests/embed-basic-test.html

Comment 1

[Bradley Baetz (:bbaetz)]

How are you using mfcembed? This is probably a packaging problem like last time
- see bug 88379. Make sure that your build includes directory.xul, directory.js,
and directory.html.

Comment 2

[Aaron Leventhal]

I'm using the one in mozilla\dist\win32_d.obj\embed.
I built it by going to mozilla\embed\config and doing nmake -f makefile.win.

Those files you mention didn't get packaged up.

Comment 3

[Bradley Baetz (:bbaetz)]

Thats the bug then. If you edit the embedding files to include those, does it work?

Comment 4

[Aaron Leventhal]

I tried putting directory.xul, .js and .html from the xpfe directory into the
Embed directory and it didn't help.

I don't see how directory.* could be the right files, because it works when I
run it from mozilla\dist\win32_d.obj\bin, and those files aren't anywhere in
that directory subtree.

Actually, there is a file called directory.xpt that was in
mozilla\dist\win32_d.obj\bin\components, but moving it into the Embed directory
didn't help either.

Comment 5

[Bradley Baetz (:bbaetz)]

well, you actually need those files in the jar - add them to the appropriate .mn
file.

you also need libappcomps.so
Ping me when you get in, and I'll stop by and take a look.

Comment 6

[Bradley Baetz (:bbaetz)]

not only aren't the directory.* files present, appcomps.dll seems to be missing
as well. This is a build config problem

Comment 7

[Chak Nanga]

MfcEmbed was mainly intented to show embeddors how to use the most common
embedding interfaces i.e. it's not intended to imitate full browser
functionality like Mozilla.

While features such as this one are useful to certain customers, a vast majority
of them do not care. Also, adding these type of features increase the size of
the embed package as well - which we're trying to minimize.

If there's a real need for some customer on how to implement this we can
probably handle that as a special case for that user - rather than complicating
our base embed packaging.

Marking WONTFIX.

Comment 8

[Aaron Leventhal]

Thanks Chak, that's fine with me.
Perhaps we can document how it's done if embeddors want it.

The only reason I reported the bug was due diligence after being asked to
smoketest an mfcembed change.