From calidion at gmail.com  Thu Sep 11 00:02:12 2014
From: calidion at gmail.com (=?UTF-8?B?5p2O55m9fOWtl+S4gOaXpQ==?=)
Date: Thu, 11 Sep 2014 15:02:12 +0800
Subject: [imps] how about FileList files.remove(item)?
Message-ID: <CAKEKHHYNoM+QZXuoOJSixpZnqqcu1o=Zwk1jF_iHy88i5NZAxg@mail.gmail.com>

hi, all

i am not sure if it is a proper place for me to post.
if you are bothed, please ignore this message.

I am recently implementing a function that needs to be able to select and
unselect images.
current input file is ok for select images,  and with FileReader it is very
easy to show images selected.

But when i want to unselect and remove specific images, it becomes a lot
complicated.

I binged (google is blocked from china currently) the web, and found the
same question:
http://stackoverflow.com/questions/9575877/file-upload-remove-value-from-input-box

the solution is to dynamically create hidden input to contain the files.

it seems ok but too complicated to do so.

I also checked the FileList Api, found there is no method to remove the
files separately.

https://developer.mozilla.org/en/docs/Web/API/FileList

as more and more ajax based web app will come up, the needs for unselect a
uploading image will become more and more common.

so I would like to propose that web support FileList remove a file .

thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/implementors-whatwg.org/attachments/20140911/5c962db6/attachment.htm>

From rancid.iodine at gmail.com  Thu Sep 18 09:59:40 2014
From: rancid.iodine at gmail.com (Rancid Iodine)
Date: Thu, 18 Sep 2014 17:59:40 +0100
Subject: [imps] differing results from our validator.nu instance and
	validator.w3.org's
Message-ID: <CABzn3dXZcvKwEOXcNuzyjJ7oueuWLE088C2=aaRhKDkbUd-mAw@mail.gmail.com>

Hi Michael and everyone else on the list.

I was wondering why we have different results again on our validator.nu
instances from that found on http://validator.w3.org . Last time it turned
out the startup flags had changed on the build.py ... we are using the
following still:

python ./build/build.py --follow-w3c-spec
--presets-file="nu-validator-site/presets.txt" all &

This is a summary of the extra errors we are not expecting:


   1. [image: Error] *Line 1, Column 456*: Bad value viewport for attribute
   name on element meta: Keyword viewport is not registered.

   ?dth=device-width, initial-scale=1.0" /*>*    <script
type="text/javascript" src=?

   Syntax of metadata name:A metadata name listed in the HTML specification
   <http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#standard-metadata-names>
   or listed in the WHATWG wiki <http://wiki.whatwg.org/wiki/MetaExtensions>.
   *You can register metadata names on the WHATWG wiki
   <http://wiki.whatwg.org/wiki/MetaExtensions> yourself.*
   2. [image: Error] *Line 56, Column 6072*: Bad value viewport for
   attribute name on element meta: Keyword viewport is not registered.

   ?dth=device-width, initial-scale=1.0" /*>* <script
type="text/javascript"> if (na?

   Syntax of metadata name:A metadata name listed in the HTML specification
   <http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#standard-metadata-names>
   or listed in the WHATWG wiki <http://wiki.whatwg.org/wiki/MetaExtensions>.
   *You can register metadata names on the WHATWG wiki
   <http://wiki.whatwg.org/wiki/MetaExtensions> yourself.*
   3. [image: Error] *Line 56, Column 6456*: Bad value
   msapplication-tap-highlight for attribute name on element meta: Keyword
   msapplication-tap-highlight is not registered.

   ?plication-tap-highlight" content="no"/*>*              <noscript>
<style type="t?

   Syntax of metadata name:A metadata name listed in the HTML specification
   <http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#standard-metadata-names>
   or listed in the WHATWG wiki <http://wiki.whatwg.org/wiki/MetaExtensions>.
   *You can register metadata names on the WHATWG wiki
   <http://wiki.whatwg.org/wiki/MetaExtensions> yourself.*

It doesn't look like anything has changed on the frontend markup validator
code either, hence the question. :D

Many thanks,

Andrei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/implementors-whatwg.org/attachments/20140918/77a5b55e/attachment.htm>

From mike at w3.org  Sun Sep 28 06:29:01 2014
From: mike at w3.org (Michael[tm] Smith)
Date: Sun, 28 Sep 2014 22:29:01 +0900
Subject: [imps] differing results from our validator.nu instance and
 validator.w3.org's
In-Reply-To: <CABzn3dXZcvKwEOXcNuzyjJ7oueuWLE088C2=aaRhKDkbUd-mAw@mail.gmail.com>
References: <CABzn3dXZcvKwEOXcNuzyjJ7oueuWLE088C2=aaRhKDkbUd-mAw@mail.gmail.com>
Message-ID: <20140928132901.GX26974@jay.w3.org>


Rancid Iodine <rancid.iodine at gmail.com>, 2014-09-18 17:59 +0100:

> Hi Michael and everyone else on the list.
> 
> I was wondering why we have different results again on our validator.nu
> instances from that found on http://validator.w3.org . Last time it turned
> out the startup flags had changed on the build.py ... we are using the
> following still:
> 
> python ./build/build.py --follow-w3c-spec
> --presets-file="nu-validator-site/presets.txt" all &
> 
> This is a summary of the extra errors we are not expecting:
> 
> 
>    1. [image: Error] *Line 1, Column 456*: Bad value viewport for attribute
>    name on element meta: Keyword viewport is not registered.

I think that may have been due to the whatwg wiki having been switched over
to TLS-only recently, and I had not updated a script I wrote that generates
https://help.whatwg.org/extensions/meta-name/ to take the switch into account.

But I have now done that and everything should be back to normal. If not,
let me know.

  --Mike

-- 
Michael[tm] Smith http://people.w3.org/mike