This issue has been closed, based on the WG's agreement on August 26.
Please see the following for details:
<http://www.w3.org/2008/08/26-wam-minutes.html#item11>
-Regards, Art Barstow
On Jul 4, 2008, at 3:46 AM, ext Thomas Roessler wrote:
My reaction is that this is local error handling and therefore out
of scope for the specification.
--
Thomas Roessler, W3C <[EMAIL PROTECTED]>
On 2008-07-04 03:29:37 +0000, Web Applications Working Group Issue
Tracker wrote:
From: Web Applications Working Group Issue Tracker <sysbot
[EMAIL PROTECTED]>
To: public-webapps@w3.org
Date: Fri, 4 Jul 2008 03:29:37 +0000 (GMT)
Subject: ISSUE-34: What happens when one runs out of storage space
when decompressing a widget? [Widgets]
Reply-To: Web Applications Working Group WG <public-webapps@w3.org>
List-Id: <public-webapps.w3.org>
X-Spam-Level:
Archived-At: <http://www.w3.org/mid/
[EMAIL PROTECTED]>
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.496200,
version=1.1.6
ISSUE-34: What happens when one runs out of storage space when
decompressing a widget? [Widgets]
http://www.w3.org/2008/webapps/track/issues/
Raised by: Josh Soref
On product: Widgets
When extracting the file data from a file entry, there is a chance
that the storage device may run out of space. How should a widget
user agent respond?
