XPC.mfasl
Georg Maaß
the file XPC.mfasl is part of the user profile. Who is responsible for
invalidating this file i.e. after updating a *.jsm file? Changes to the
JavaScript module in a *.jsm file are not populated to the application
until the file XPC.mfasl has been deleted. Is there an API to tell
XulRunner to invalidate this file for all users on next application
start? Deleting it via nsILocalFile might work for the current user, but
should fail for the file in other users profile for security reasons. So
I want to know whether there is an API to invalidate the file globally
to invoke Xulrunner to recreate it for each user on his next application
start.
MDC paces related to JavaScript modules do not mention such an API, or I
have tomatoes on my eyes. Probably there is a scriptable API, but I did
not yet detect it.
Best wishes, Georg
Boris Zbarsky
> the file XPC.mfasl is part of the user profile. Who is responsible for
> invalidating this file i.e. after updating a *.jsm file?
Whoever updated the file. Typically such files are only changed when
extensions are installed or uninstalled or the app is updated; as part
of the component reregistration this triggers this file is invalidated.
> Is there an API to tell
> XulRunner to invalidate this file for all users on next application
> start?
You might want to ask in .platform; XPC.mfasl isn't part of the JS engine.
-Boris