But for me, the overriding factor that places blame squarely on the College Board is this from the article: For starters, the College Board could've done a much better job emphasizing this step for iOS users in its instructions page. I agree the HEIC thing is very confusing (having set up my parents' phones recently), but I can't see how Apple is to blame. Would it be correct for iOS Safari to quietly reencode to jpeg when a HEIC file is uploaded via a webform? How would Safari know that the site's backend didn't want an HEIC file? So "not using the `accept` attribute" has to retain semantics that are backward-compatible with that legacy. All these existed on the web, and used, before the `accept` attribute was introduced. a computer-forensics or antivirus-signature portal, that wants an evidence file or the interface to a hex editor or decompiler, that expects a raw binary with arbitrary extension in unknown format or the SCP component of an old web SSH terminal emulator. It wants the thing on the other side sent to it as-is.Īnd, it's important to support those semantics (and that particular implicit meaning for leaving out the `accept` attribute), because such "as-is" uploads have many use-cases. Just like when a client requests `Cache-Control: no-transform` from a server. And so it has the semantics of taking whatever file you provide it as-is, with no transformation necessary. Which, in turn, means that the form isn't putting any constraint on what's being uploaded at all, and so there's no reason to think that the form is asking for an image in the first place. Turns out that's too much to ask their process is "get the image from your camera to your test-taking device whichever way you can think of, not our problem." Not surprisingly that's not a very foolproof process.)īecause a lack of an accept attribute on the file-input element has a defined meaning in HTML, and that meaning is accept="⋆/⋆".
#Iphone heic converter code#
(A bit more context on my original comment: I thought they had some working system where test takers could upload photos directly from their phones - e.g., scan a QR code to open a page with a unique ID with an image upload form. In any case, sounds like absolutely horrid QA and communications of what's accepted (and of course, very bad idea not supporting the format in the first place when half your test takers are taking pictures in that format). The article isn't clear on what exactly was happening before, but I suppose students were trying to submit airdropped. png/.jpeg to bypass the extension check (who would have guessed extensions don't have to correspond to file types), they went through but were rejected a day later. Some students (after the issue was known) airdropped photos to their computers and attempted to rename. Turns out I overlooked some details in the article. Return flask.render_template("index.html") In case anyone's interested, source code you can use to test for yourself (a Flask app): To be clear, on macOS you need to select from Photos instead of the filesystem for this to take effect. This is true on both macOS and iOS Safari (latest). screenshots) from Photos are converted to JPEG automatically. Ten bucks says College Board programmer(s) failed to do the most basic and standard filtering.Įdit: Like a sibling comment said, the accept attribute actually isn't necessary even PNG images (e.g. Selected a HEIC file from Photos in Safari, the selected image was automatically converted to JPEG. Tried a standard input tag with the proper accept attribute A national testing portal ought to support the default image format taken by the world's most popular phone, period. Just curious for the technical details of who's more to blame here - Apple not providing enough backwards compatibility, or the testing portal being designed poorly.īecause blaming students for not following obscure instructions to change their phone's overall configuration is not the right path.
Or was the portal programmed badly or in a non-standard way that that couldn't happen? Or is there a way to do it that the developers ignored? I'm just curious technically why the same didn't happen with the testing portal? If you have a webpage that accepts image uploads, is iOS Safari not smart enough to do the same conversion? > iPhones convert HEICs to JPEGs automatically when they’re attached to emails in the Mail app I thought iOS was supposed to convert HEIC images to JPEG automatically behind-the-scenes in any file transfer situation where HEIC isn't supported.
0 kommentar(er)
