Bug 696994 - Mylyn attachments don't open in browser
Summary: Mylyn attachments don't open in browser
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 14:28 UTC by Andrew Overholt
Modified: 2012-04-12 16:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-12 16:41:13 UTC
Type: ---


Attachments (Terms of Use)

Description Andrew Overholt 2011-04-15 14:28:29 UTC
In a Mylyn task rich editor one can click on attachments and they are supposed to open in the browser (if you choose that; I believe it's the default, too).  Using these packages:

eclipse-swt-3.6.2-2.fc15.x86_64
eclipse-mylyn-3.4.2-5.fc15.noarch

if I open an attachment such as an image (ex. the image attachments on https://bugzilla.redhat.com/show_bug.cgi?id=684894) a browser view opens but then a file chooser dialogue is presented with no indication as to why.  I guessed that it was asking me where to save the file so I entered test.png and sure enough it saved the file correctly.  I seem to remember Mylyn doing something more intelligent with attachments than just offering to save them without any indication of that's what it was trying to do.  Could this have something to do with our WebKit usage?

Comment 1 Alexander Kurtakov 2012-04-12 10:33:59 UTC
To clarify this works for text attachments so it might be somehow related to content handlers registration.

Comment 2 Andrew Overholt 2012-04-12 16:41:13 UTC
(In reply to comment #1)
> To clarify this works for text attachments so it might be somehow related to
> content handlers registration.

I think you're right and I think this is an upstream bug.  I don't have time to do further investigation at this time so closing.


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