Not gone, but that's the direction we're heading (hopefully).
> it may currently still be best to use a framework or library to present these, or to use a custom input of your own. Another option is to use separate date and time inputs, each of which is more widely supported than datetime-local
That's because by design <input> does not let you configure a timezone (EDIT: nor a datetime format), and it's always somehow badly detected/misconfigured on a small subset of your users. Later you find out the user thought they were entering a DD/MM/YYYY date, while the browser decided it's getting MM/DD/YYYY, and hijinks ensue. It's easy to ensure the correct timezone on js pickers.
It is anecdotal but we had a JPEG at ~115KB and after encoding to AVIF the quality remained the same but the file size dropped to ~15KB.
Having looked at caniuse.com it seems that Chrome, Opera and (only just now by default) Firefox support it. With Edge, Safari, and the majority of mobile browsers still to catch up.
What's extra sad about that is WebKit supports AVIF images, but Safari doesn't because it hands image decoding off to the OS where it isn't supported. Works in Gnome's WebKitGTK though.
I did a small trial of AVIF (using the AVIF plugin for pillow) with high quality photographs and got much worse results than WEBP. (Much bigger file that looked much worse.)
It could be my encoder sucks, could be I didn’t pick the right settings (command line opts look like the engineer’s console on the original 747). Most of the demos I have seen online with AVIF images are highly compressed images that look awful on close inspection. Maybe you can accept that for video but I can’t for my photographs.
I have experienced the same, though I’ve done less visual comparisons. Comparing % quality like-for-like between webp and avif, on average avif files are slightly larger than webp counterparts.
Things didn’t materially improve when using high compression (slow) encoding settings. Could have been a bad encoder (libavif iirc)— there might be an explanation but on the face of it I saw worse performance than webp.
Have you tried containers? I used to rely heavily on profiles, but containers are like having several profiles open at once, or several degrees of private browsing.
Only as long as there is a "no profile" option that will still save history and cookies. You know, like a browser before all the crap came along.
It appears to me that Google Chrome only has the option of "fully logged in with GSuite account where we track every damn thing you do" and "Guest" which is just private browsing, won't save any state, making it inconvenient.
I would trade all these things, in a heartbeat, for the ability to keep other tabs/windows working when one tab is in a hard loop. That one facility is the thing that means I can't let go of Chrome, even though Firefox is prefereable in so many other way.
Lots to see but still no ipv6 support in the adresse bar. What I mean is that you can write http://192.168.1.1 to access some page but you can't type some ipv6 adresse format
I'll check Firefox again when they get rid of the leeching managing team going from blunder to blunder, and from unrelated to a web browser pursuit to another...
My favorite thing about Firefox is containers. It also has a more generous addon policy, for instance the Bypass Paywalls Clean extension which Google won't allow on the Chrome store.
Talk about a clickbait title. Two hyper-technical features and support for an obscure image format.
To be honest, as a faithful Firefox user, I'm very hesitant to update my browser. A few months ago FF rolled out an abysmal UI update out of the blue, and I had to rely on third-party "fix" [0] to this problem. I really don't want to lose the "fix" due to update, the low contrast of default theme makes Firefox just unusable to me.
I wish there was a no-bullshit fork of Firefox with no Pocket, no Suggestions and Photon UI.
Why not just turn off "Contextual suggestions"? Using unpatched version of browser is very risky these days. Or at least use Firefox ESR, that receives security patches, but lags on features.
Pretty much unequivocal good if you want state-of-the-art compression and live in a country that enforce patents. The Wikipedia page for AV1 explains it well I think: https://en.wikipedia.org/wiki/AV1#Purpose
> The SHA-256 algorithm is now supported for HTTP Authentication using digests. This allows much more secure authentication than previously available using the MD5 algorithm.
Lol wat?
For reference - in a password hashing context, you generally don't care about about collisions. Its not really a relavent attack.
What you do care is speed and memory hardness. Generally you want a slow hash, like bcrypt or argon2, so that in an offline attack the attacker can't bruteforce very quickly.
[+] [-] caterama|4 years ago|reply
I've been out of frontend web dev for a while... does this mean the days of trying to find/create your own (good) datetime picker component are gone?
[+] [-] greggturkington|4 years ago|reply
> it may currently still be best to use a framework or library to present these, or to use a custom input of your own. Another option is to use separate date and time inputs, each of which is more widely supported than datetime-local
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in...
[+] [-] yyyk|4 years ago|reply
That's because by design <input> does not let you configure a timezone (EDIT: nor a datetime format), and it's always somehow badly detected/misconfigured on a small subset of your users. Later you find out the user thought they were entering a DD/MM/YYYY date, while the browser decided it's getting MM/DD/YYYY, and hijinks ensue. It's easy to ensure the correct timezone on js pickers.
[+] [-] newhotelowner|4 years ago|reply
It won't look and behave like how designers wanted in your company. It will look different in different browser and OS.
[+] [-] jablala|4 years ago|reply
Having looked at caniuse.com it seems that Chrome, Opera and (only just now by default) Firefox support it. With Edge, Safari, and the majority of mobile browsers still to catch up.
[+] [-] wlesieutre|4 years ago|reply
https://www.coywolf.news/webmaster/why-webkit-supports-avif-...
[+] [-] PaulHoule|4 years ago|reply
It could be my encoder sucks, could be I didn’t pick the right settings (command line opts look like the engineer’s console on the original 747). Most of the demos I have seen online with AVIF images are highly compressed images that look awful on close inspection. Maybe you can accept that for video but I can’t for my photographs.
I was disappointed.
[+] [-] joe_hoyle|4 years ago|reply
Things didn’t materially improve when using high compression (slow) encoding settings. Could have been a bad encoder (libavif iirc)— there might be an explanation but on the face of it I saw worse performance than webp.
[+] [-] bloopernova|4 years ago|reply
https://www.waterfox.net/
[+] [-] miralize|4 years ago|reply
[+] [-] ASalazarMX|4 years ago|reply
[+] [-] Crono|4 years ago|reply
Together with the integrated profile manager (Firefox.exe -p) its a really nice solution!
[+] [-] skrtskrt|4 years ago|reply
It appears to me that Google Chrome only has the option of "fully logged in with GSuite account where we track every damn thing you do" and "Guest" which is just private browsing, won't save any state, making it inconvenient.
It's creepy and presents false choice.
[+] [-] syntaxing|4 years ago|reply
[+] [-] kreeben|4 years ago|reply
[+] [-] CraftThatBlock|4 years ago|reply
[+] [-] strifey|4 years ago|reply
[+] [-] MikeTaylor|4 years ago|reply
[+] [-] zfxfr|4 years ago|reply
[+] [-] mariusor|4 years ago|reply
[+] [-] coldtea|4 years ago|reply
[+] [-] 21eleven|4 years ago|reply
Also it is an all around good browser.
[+] [-] davidgerard|4 years ago|reply
[+] [-] NelsonMinar|4 years ago|reply
[+] [-] unknown|4 years ago|reply
[deleted]
[+] [-] Causality1|4 years ago|reply
[+] [-] iakov|4 years ago|reply
To be honest, as a faithful Firefox user, I'm very hesitant to update my browser. A few months ago FF rolled out an abysmal UI update out of the blue, and I had to rely on third-party "fix" [0] to this problem. I really don't want to lose the "fix" due to update, the low contrast of default theme makes Firefox just unusable to me.
I wish there was a no-bullshit fork of Firefox with no Pocket, no Suggestions and Photon UI.
[0] https://github.com/black7375/Firefox-UI-Fix
[+] [-] bloopernova|4 years ago|reply
[+] [-] unknown|4 years ago|reply
[deleted]
[+] [-] throwaway123x2|4 years ago|reply
[+] [-] LeoNatan25|4 years ago|reply
[+] [-] pengaru|4 years ago|reply
Epiphany needs a noscript equivalent so I can retire FF.
[0] https://en.wikipedia.org/wiki/Juno_Online_Services
[+] [-] bloopernova|4 years ago|reply
[+] [-] unknown|4 years ago|reply
[deleted]
[+] [-] jikbd|4 years ago|reply
[deleted]
[+] [-] alittlesalami|4 years ago|reply
[+] [-] ketralnis|4 years ago|reply
[+] [-] haurra|4 years ago|reply
[deleted]
[+] [-] kreeben|4 years ago|reply
Turn off auto updates here: options-->general-->firefox updates
[+] [-] butz|4 years ago|reply
[+] [-] AdmiralAsshat|4 years ago|reply
Is "royalty-free" an unequivocal good, or a good with caveats?
I would assume it means you don't have to pay licensing to encode or decode the format. Are there any restrictions?
[+] [-] belval|4 years ago|reply
[+] [-] jagger27|4 years ago|reply
[+] [-] bawolff|4 years ago|reply
Lol wat?
For reference - in a password hashing context, you generally don't care about about collisions. Its not really a relavent attack.
What you do care is speed and memory hardness. Generally you want a slow hash, like bcrypt or argon2, so that in an offline attack the attacker can't bruteforce very quickly.
Sha256 is almost as bad as md5 in this context.