810391 - ArchiveReader enabled on b2g

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Andrea Marchesini [:baku]]

Probably ArchiveReader should be enabled by default for b2g.

Comment 1

[Andrea Marchesini [:baku]]

Attachment: patch

Comment 2

[Mounir Lamouri (:mounir)]

Why do we want to enable the ArchiveReader on b2g by default? B2G is as much part of the Web than Firefox. I don't think we should push stuff there that are not ready.

Comment 3

[Andrea Marchesini [:baku]]

In general I agree with you. But ArchiveReader is ready :) It's not just standardized. 
I'm in contacts with developers who are using it for B2G mostly for EBook readers.

I think ArchiveReader must be enabled on B2G.
If not, we must have bugs explaining why this is not ready.

Comment 4

[mathieu]

I'm one of those developpers :) too sad my demo is not working, I'm at #mozfest and I can brag about it!

But there is something I don't understand: this was on B2G earlier and it's not anymore? at least in my few day B2G builds and in Firefox Nightly

Comment 5

[mathieu]

/can/can't/

Comment 6

[Mounir Lamouri (:mounir)]

(In reply to Andrea Marchesini (:baku) from comment #3)
> In general I agree with you. But ArchiveReader is ready :) It's not just
> standardized. 

Unfortunately, it's more complex than "ready but not standardized". We have no idea if that will ever be standardized. No one expressed an interest on this API during TPAC and Apple expressed clear doubts regarding use cases (arguing that other APIs could solve those).

> I'm in contacts with developers who are using it for B2G mostly for EBook
> readers.

It would be interesting to hear why ArchiveReader is used. What is used on Webkit to do the same thing?

Comment 7

[Andrea Marchesini [:baku]]

There are some JS libraries for opening zip archive. zip.js is one of them.
The main reasons why we have this ArchiveReader are:

. it doesn't block the main thread
. it can be extended in order to support new archive formats (Gz, Tar, Rar, etc).

Comment 8

[mathieu]

Hi, why it's used (in my case) for an ebook reader is that epub are zipped files

I'll be (re)adding an alternative using js libs, but the few I tested are really slower. for some ebooks it means it takes almost a minute to open instead of 1~2 seconds on a mobile device (nexus s with FirefoxOS) 
Moreover, the existing js libraries are blocking the main threads which mean one cannot abort the unzipping and the page/app seems crashed meanwhile

Comment 9

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

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

Review of attachment 680143 [details] [diff] [review]:
-----------------------------------------------------------------

Yeah, we should keep B2G in sync with Firefox regarding what we expose to the web platform as much as possible. If we don't think that ArchiveReader is ready for Firefox, then it's also not ready for B2G.

I'm personally still in favor of the prefixing approach, in both places, but I appear to be in shrinking company there.

Comment 10

[Andrea Marchesini [:baku]]

I'd submit a new patch enabling the ArchiveReader by default and prefixing it if we agree on it.

Comment 11

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

I'm still of the opinion that we should keep B2G and Firefox desktop in sync. And that the only way we're going to actually get feedback on this is by enabling it in release builds.

Comment 12

[Mounir Lamouri (:mounir)]

The current discussion in dev-platform shows a clean will to remove prefixes in favour of not enabling features in releases builds. Better to try to follow this policy I believe.

Comment 13

[Andrea Marchesini [:baku]]

Mark as wontfix.