Bug 67004

Summary:	MIME Type on First Reporting Not Auto Detected
Product:	freedesktop.org	Reporter:	Joel Madero <jmadero.dev>
Component:	Website	Assignee:	fd.o Admin Massive <sitewranglers>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	major
Priority:	medium	CC:	foss, jmadero.dev, qubit
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Joel Madero 2013-07-17 15:46:25 UTC

Hi All,

In the past LibreOffice requested that attachments be auto detected for MIME type. This change was done and now MIME types are detected but only for attachments attached after the bug is reported (ie. additional attachments)

Steps:

Go to https://bugs.freedesktop.org/

File a Bug

LibreOffice

Fill in test info - select "add an attachment"

Select a doc(x) or xls(x)


Expected:
MIME type detected

Observed:
They get filed as plain text, there isn't a way around this and it creates a bit of a headache for people on the contributor side as we either have to:

a) Change the mime type - which isn't the easiest to do
b) Right click -> Download then open the file

for new contributors they often times don't know about this workaround so they are unsure how to open the plain text documents (that are really not plain text but just detected incorrectly)


Thanks for the infra support.

Comment 1 Thomas Hackert 2013-11-04 05:29:02 UTC

Hello Joel, *,
I can confirm this issue with Firefox 28.0a1 (2013-11-03) under Debian Testing AMD64 ... :( When I created https://bugs.freedesktop.org/show_bug.cgi?id=71192 yesterday, I discovered, that the attachment I have attached directly has changed its MIME type from image/png to text/plain ... :( This may also be the reason, why a lot of attachments are set to plain/text and QAers have either to edit the MIME type first or find a way to download it otherwise. I think, this is a too big hurdle for potentially new QAers ... :(
HTH
Thomas.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.