WHATWG on 2024-10-17

08:46	<gamicord>	Normally, we teach kids HTML, CSS and JavaScript, using just NotePad, Notepad++ and a Web browser. And most times, we do this without an internet connection, without having a server, and without having a backend like NodeJS, WAMP, or XAMPP. The challenge I have, is that I want to teach these kids the Download Functionality. But when we add the "Download Attribute" to the href of our Anchor Tag, the file doesn't download. Rather, it opens up in a new Tab or window. What I found out, is that, the "Download Attribute" doesn't work on the Local file system. This is the same issue here on GitHub---https://github.com/mozilla-mobile/firefox-ios/issues/13299 Since we are moving some things into HTML and CSS according to this talk-- https://youtu.be/IP_rtWEMR0o In which case, things like Dialog (modal) are now tags in HTML. MY REQUEST Add parameters to the "Download Attribute" --- where we can specify the source of the downloadable file. Parameters like "localfile", "server", "domain", "filesystem". These parameters to the Download Attribute, makes it more versatile and capable. --"localfile" -- means that the fie is in the same root as the index.html file. -- "server" -- -- means that the file is hosted on a Web Server. In this case, it will only allow for absolute URL in the href. -- "domain"-- means that the file is hosted on a Web Server of same-origin. In this case, it can allow for relative URL in the href. -- "filesystem"---- means that the file is hosted on a Laptop or Personal Computer(PC). This should allow the Download Attribute to still download the file, using relative URL in the href. THE CHALLENGE I am not able to download from my Local File system, not able to download within my PC with the Download Attribute, and I have raised it on Microsoft Forum -- https://answers.microsoft.com/en-us/microsoftedge/forum/all/html5-download-attribute-is-not-working-at-all-on/6f0681ee-05b6-49f8-a0f2-9ef6b6e27460 And also on W3Schools Forum --- https://w3schools.invisionzone.com/topic/63572-html5-download-attribute-is-not-working-at-all-on-all-browsers/ MOVING FORWARD If WHATWG can add parameters as specified, or parameters that they see fit, which can allow us use the Download Attribute to natively download files from the Local File System of my Laptop or PC, I will be the most glad and grateful to WHATWG. Special Regards, as I keenly await your positive response.
13:18	<annevk>	Did anyone try to reproduce that by chance? This person also emailed `sg@`. My suspicion is that these are browser bugs and no new feature is needed.
22:37	<jamescobban>	I am a little surprised that you do not have a web server for your course, containing the course documentation. Designing web sites is intrinsically a cooperative group activity. To some extent the whole point of the Web is that it is NOT contained on your own computer. Why teach your students something they will never use outside of the class? You do not need connectivity to the outside world, just a WiFi node that all of the student's devices are connected to that also includes a workstation running a web server.
23:16	<akaster>	I'm a little confused trying to implement the Update algorithm from the service workers spec. It seems like the spec hasn't been updated to reflect the latest changes to perform the fetch hook from the HTML spec? Specifically the concept of the processCustomFetchResponse algorithm
23:16	<akaster>	For example, steps 4, 5, and 6 say this: If the isTopLevel flag is unset, then return the result of fetching request. Set request’s redirect mode to "error". Fetch request, and asynchronously wait to run the remaining steps as part of fetch’s processResponse for the response response.
23:18	<akaster>	but in the steps for dedicated workers, https://html.spec.whatwg.org/multipage/workers.html#run-a-worker, it is quite a bit clearer... If isTopLevel is false, fetch request with processResponseConsumeBody set to processCustomFetchResponse, and abort these steps. Set request's reserved client to inside settings. Fetch request with processResponseConsumeBody set to the following steps given response response and null, failure, or a byte sequence bodyBytes:
23:18	<akaster>	Should I just be assuming that steps 4,5,and 6 from service workers Update AO are written with the same language as run a worker and open a spec issue?
23:28	<akaster>	or does the service worker spec here actually want me to fetch request with `processResponse` set to the following steps?
23:28	<akaster>	(rather than processResponseConsumeBody like for shared/dedicated workers)
23:30	<Kaiido>	Did anyone try to reproduce that by chance? This person also emailed `sg@`. My suspicion is that these are browser bugs and no new feature is needed. All browsers seem to allow `download` using an in-memory source, i.e. `blob:` or `data:`. What they block is the downloading of cross-origin resources, just like when served from an actual server. The thing might be that browsers do consider `file:` as an opaque origin, and thus block even "same-folder" downloads.