User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031014 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031014 On *nix systems (I dont know if other systems allow this), Mozilla must give an option to swallow helper application, like plugger does. Reproducible: Always Steps to Reproduce: 1.Call a pdf file from browser Actual Results: A new window will be open with xpdf (if you don't use plugger) Expected Results: Open xpdf inside browser window
reporter: are you going to write the code to do this?
Assignee: general → blizzard
Component: Browser-General → GFX: Gtk
QA Contact: general → ian
Yes, if I take approval of this feature.
So the idea here is to just reimplement plugger? Why? Would it not make more sense to have distributors ship Mozilla with plugger and thus use the already existing perfectly good code to do this?
Mozilla already does what plugger does, except by swallowing apps. I think will be better if we do not need to care with configuration of plugger to do swallow and concentrate only on Mozilla. Even the distributors ship Mozilla with plugger, for administrative purposes, is more complicated manage two applications instead of one.
There is also the question of what happens if a "swallowed" app crashes. Does that affect the rest of Mozilla?
IMHO the ideal is not affect Mozilla. I think only a few apps will be run at a time and the cost of isolate these process is low. What you think about this? You see any negative aspects of this solution?
Not offhand, as long as someone writes and maintains the code....
Created attachment 133573 [details] [diff] [review] DTD changes to incorpore swallow This change affect only DTD. Soon I will send the XUL.
are you saying you can do this with just xul+js?
No way. I like to send pieces of code as a backup. I done the XUL and DTD changes, but I reviewing the XUL code. After this I will wrote the rest of code.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.