Closed Bug 638670 Opened 13 years ago Closed 13 years ago

Add 602plugin.so to list of Xt plugins that are run in process.

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking2.0 Macaw+, status2.0 .1-fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla5
Tracking Flags:
Tracking Status
blocking2.0 --- Macaw+
status2.0 --- .1-fixed

People

(Reporter: karlt, Assigned: karlt)

References

Details

(Keywords: regression, Whiteboard: [fx4-rc-ridealong])

Attachments

(1 file)

patch
846 bytes, patch
benjamin
: review+
dveditz
: approval2.0+
Details | Diff | Splinter Review 
I was contacted re the plugin at http://www.602.cz/lin/download_form_filler
It is an Xt plugin using XtWindowToWidget and XtAddEventHandler.
Apparently they have government clients.
I haven't tried the plugin.  It looks like it starts a wine process.  I don't know much more than that.

Until bug 544088 is fixed, Xt plugins will fail when run out of process, so we should add know Xt plugins to the list.
Attached patch patch — — Splinter Review 

        Attachment #516789 -
        Flags: review?(benjamin)

    
  

        Attachment #516789 -
        Flags: review?(benjamin) → review+

    
    

    
  
Requesting ".x+".

This is a pref-only change adding another plugin to an existing oop-blacklist for Xt plugins such as this plugin.  The plugin authors confirm that their plugin works fine with this preference set.  I expect the proportion of our users with this plugin is small, but the risk to those without in zero.
blocking2.0: --- → ?
Whiteboard: [asking for .x+ fx4-rc-ridealong]

    
  
blocking2.0: ? → .x+
Whiteboard: [asking for .x+ fx4-rc-ridealong] → [fx4-rc-ridealong]

    
  

        Attachment #516789 -
        Flags: approval2.0?

    
  
blocking2.0: .x+ → -

    
    

    
  
Comment on attachment 516789 [details] [diff] [review]
patch

Cancelling approval request. Please re-request approval for the release after Firefox 4, when the patch has had some time on the trunk. In the meantime, users have a workaround via the pref in the patch.

        Attachment #516789 -
        Flags: approval2.0?

    
  
Depends on: post2.0

    
    

    
  
http://hg.mozilla.org/projects/cedar/rev/e6b36ff336bb
Whiteboard: [fx4-rc-ridealong] → [fx4-rc-ridealong][fixed-in-cedar]

    
    

    
  
http://hg.mozilla.org/mozilla-central/rev/e6b36ff336bb
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [fx4-rc-ridealong][fixed-in-cedar] → [fx4-rc-ridealong]
Target Milestone: --- → mozilla2.2

    
  
No longer depends on: post2.0

    
  
blocking2.0: - → Macaw

    
    

    
  
Comment on attachment 516789 [details] [diff] [review]
patch

Approved for mozilla2.0 repository, a=dveditz for release-drivers

        Attachment #516789 -
        Flags: approval2.0+

    
    

    
  
Transplanted from mozilla-central onto releases/mozilla2.0:

    http://hg.mozilla.org/releases/mozilla-2.0/rev/471272f0e72a

          status2.0:
          --- → .1-fixed

    
  
Product: Core → Core Graveyard

          You need to log in
          before you can comment on or make changes to this bug.