- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 23 Mar 2022 01:38:30 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 23 March 2022 08:38:42 UTC
@marcoscaceres commented on this pull request. > + |manifest_url|. + </li> + <li>If |file_handler| is failure, continue. + </li> + <li>[=list/Append=] |file_handler| to |processedFileHandlers|. + </li> + </ol> + </li> + </ol> + <p> + On [=installation=], a user agent SHOULD run the process to + [=register file handlers=] + </p> + <section> + <h3> + Registering file handlers Thanks for the clarification, @evanstade. This may become contentious as it may be that there are certain file types that a web application might never be allowed to handle (e.g., system files)... but this may be a UA-level restriction or os-level. So, question is: would we allow registering anything? or would it be limited to a few well-known types (which yes, massively restricts the utility of this). -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/1005#discussion_r832992780 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/pull/1005/review/918388289@github.com>
Received on Wednesday, 23 March 2022 08:38:42 UTC