Re: [whatwg] Accessing local files with JavaScript portably and securely

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Patrick Dark > I can't see this being addressed. The only good reason to distribute an > application this way is because you want it to be confidential and there's no > incentive to accommodate what one might call "walled

Re: [whatwg] Is the "document" identifier defined in the standards?

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Kevin Chen > But I do not see a guarantee within the standards that the browser will > provide an object called "document" containing the current document object > (irrespective of the fact that this does seem to be the case in

Re: [whatwg] Subresource Integrity-based caching

Hi Alex! Glad to have you here. This is indeed a popular idea. The biggest problem with it is privacy concerns. The best summary I've seen is at https://hillbrad.github.io/sri-addressable-caching/sri-addressable-caching.html. In particular if such a suggestion were implemented, any web page

Re: [whatwg] Accessing local files with JavaScript portably and securely

From: David Kendal [mailto:m...@dpk.io] > This is getting silly. > says the WHAT WG's purpose is to 'evolve the Web'; since file: URIs are part > of the web, this problem falls within the WHAT WG's remit. file: URLs are part of the web, e.g. parsing

Re: [whatwg] Accessing local files with JavaScript portably and securely

From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of > You are continuing to dodge this problem by redefining the WHAT WG's > responsibilities. Please don't do that. I don't intend to take direction on how I spend my time from you. I'd be curious as to whether you can find any

Re: [whatwg] readonly attribute

Hi Jonathan, sorry for the delay in responding here. > This doesn't quite jive with my understanding of the distinction between > `readonly` and `disabled` - to me, "readonly" and "disabled" controls can both > not be edited by the user, but "readonly" means that the value will be > included in

Re: [whatwg] rel=bookmark

Hi Ed, (Remember to use the HTML Standard, located at https://html.spec.whatwg.org/multipage/links.html#link-type-bookmark, not any forks of it.) Right now the bookmark link relation has a specific purpose, as you can read in the spec: > The bookmark keyword gives a permalink for the nearest

<    1   2