1065944 - [B2G][E-mail] PDF view or download

Status: RESOLVED DUPLICATE of bug 825318

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Marek Raida]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140825202822

Steps to reproduce:

I've received email with PDF attachment


Actual results:

Without being able to open the document, download the document or even forward the email with document. I'm time pressed and I need to read the document somehow, but on current B2G (2.0) I'm completely frustrated and unable to do anything with the document :-((((


Expected results:

I expect to be able to do every of mentioned actions (view, download and forward), but having at least one of them would make it usable - right now it is utterly failing user experience case :-(((

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

Duping to the bug about supporting other types of attachments, but see also bug 912002 for forwarding attachments.  We're expecting to address both of these things for version 2.2.  I agree that the current situation sucks and it's fairly ridiculous that we still don't support these features at this time.

Comment 2

[Marek Raida]

Andrew, you are right, and sice there is no fixed roadmap for 2.0 yet - who/how can we in best way epress our needs and laments to increase chance that specific feature or bugfix fill be put on the 2.2 roadmap, please? 
Marek

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

Forwarding attachments was a 2.1 feature that got bumped to 2.2 so we could stabilize the email app and address some technical debt that was making things brittle.  It will definitely be in 2.2 and its prerequisites overlap so extensively with supporting saving any/all attachments to the download manager that that is also a near-lock for 2.2 on that basis.  For that reason and the PDF reason I'll also make sure that we explicitly prioritize that as an early feature for v2.2.

And actually, there's a good chance we'll land implementations prior to the start of the formal start of the v2.2 feature development push, although exactly when depends on how many blockers show up for v2.1 in the near-medium future.