- From: Erik Bruchez <erik@bruchez.org>
- Date: Wed, 13 Feb 2013 10:24:31 -0800
- To: Ulrich Nicolas Lissé <unlisse@gmail.com>
- Cc: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>, Forms WG <public-forms@w3.org>
- Message-ID: <CAAc0PEXaXzyVO1GrvYgzbjKCAkL_dRMP9t+kp3prjVA+uqfWnw@mail.gmail.com>
All, In today's call we haven't yet resolved to adopt upload/@accept, but to summarize I am in favor for the following reasons: - internal consistency: (and here @mediatype and the child mediatype element clash) - consistency with HTML: @accept is in HTML [1] and HTML Living Standard elaborates on it [2] - support in browsers was poor until not long ago but is now coming, see highest rated answer here [3] I tried the demo linked from [3] and it's working with recent versions of Chrome and Firefox. This means that it's easy to support this feature now in browser-based XForms implementations. -Erik [1] http://www.w3.org/TR/REC-html40/interact/forms.html#adef-accept [2] http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#file-upload-state-(type=file) [3] http://stackoverflow.com/questions/181214/file-input-accept-attribute-is-it-useful#answer-10503561 On Wed, Feb 13, 2013 at 5:41 AM, Ulrich Nicolas Lissé <unlisse@gmail.com>wrote: > Nick, > > I'm sorry to cause trouble, but I thought we had consensus about > xf:upload/@accept. But reading > http://www.w3.org/2013/02/06-forms-minutes.html I realize we had no > official approval. So, of course we should discuss this topic today. > > That being said, I don't see problems editing the Wiki. We have > http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&action=history and > can always revert changes. > > Regards, > Uli. > > > On Wed, Feb 13, 2013 at 2:08 PM, Nick Van den Bleeken < > Nick.Van.den.Bleeken@inventivegroup.com> wrote: > >> I have a remark not related to the text itself. But I find it really >> dangerous to propose text in the live specification. In wiki land you don't >> have something like branches and so all modifications are made in the same >> version, which makes it impossible to know if the change is 'approved' by >> the group or not. >> >> Certainly in this late stage in the process I would __not__ recommend >> making changes to spec that aren't editorial or backed with a >> resolution/consensus. >> >> Could we discuss this during the call? >> >> Kind regards, >> >> Nick Van den Bleeken >> R&D Manager >> >> Phone: +32 3 425 41 02 >> Office fax: +32 3 821 01 71 >> nick.van.den.bleeken@inventivegroup.com >> www.inventivedesigners.com >> >> >> >> On 13 Feb 2013, at 13:51, Ulrich Nicolas Lissé <unlisse@gmail.com> >> wrote: >> >> Dear Group, >> >> i completed https://www.w3.org/2005/06/tracker/xforms/actions/1931. >> Please review >> http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3775&oldid=3774 >> . >> >> Regards, >> Uli. >> -- >> Ulrich Nicolas Lissé >> >> >> >> >> >> ------------------------------ >> >> Inventive Designers' Email Disclaimer: >> http://www.inventivedesigners.com/email-disclaimer >> > > > > -- > Ulrich Nicolas Lissé >
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
Received on Wednesday, 13 February 2013 18:25:19 UTC