callahad

58 ms·

271.
by callahad 7y ago
Even better: it's not actually taxpayer money. The repatriation is funded by a mandatory £2.50 surcharge on all package holiday bookings that's been in place since 1973. https://www.caa.co.uk/ATOL-protection/C
272.
by callahad 7y ago
Yep! We're still working on how in-browser debugging should work, but we'll get there. This post is specifically "Debugging WebAssembly Outside of the Browser," but the title on HN was unfortunately truncated.
273.
by callahad 7y ago
Mainly because things might work differently in a WASM runtime than they would in native code. A chief example is filesystem access. The WebAssembly System Interface ( https://wasi.dev ) uses capability-based access to files, so W
274.
by callahad 7y ago
The UI is open source, but the mailsync engine it uses is distributed as a proprietary, closed-source binary.
275.
by callahad 7y ago
Vengefulduck's description is accurate: 1. Signing is required via a compile-time flag for official builds of Firefox and Firefox Beta. 2. Signing is optional in other builds of Firefox (Unbranded, Developer Edition, and Nightly), and
276.
by callahad 7y ago
Support for add-ons will not be removed from Firefox for Android ("Fennec"). However, Fennec will eventually get discontinued (but not in the next year), because its code is honestly a mess. So the question is whether or not Fen
277.
by callahad 7y ago
Not exactly. I understand "EOL" to mean that all support has ended. An EOL'd project is dead, and if anything breaks no one is going to fix it for you. That is not the case for Firefox for Android. Instead, think of Firefox
278.
by callahad 7y ago
> clearly are targeting this new replacement browser for version 69 in a few months. That is incorrect, and stems from a misunderstanding of our release model. > What they haven't done is given a clear statement. The clearest
279.
by callahad 7y ago
We did make a statement mostly to that effect on the dev-platform list back in April: https://groups.google.com/forum/#!topic/mozilla.dev.platform... It got picked up by a handful of news outlets, but there's
280.
by callahad 7y ago
I can't make any specific commitment, but there's a lot of time between now and Firefox for Android going EOL (and we haven't committed to specific timing for that, either.) However, we do have concrete plans for supporting
281.
by callahad 7y ago
Fennec is moving to an Extended Support Release model so we can focus on Preview. This means that the engine will remain at major version 68 for the next year, but it will still receive security updates and bugfixes. And it will continue to
282.
by callahad 7y ago
Hi. I work for Mozilla. Firefox for Android is not dead. You are free to continue using it. It will continue to support add-ons, and it will receive regular security updates and bugfixes for at least the next year. We are focusing all
283.
by callahad 7y ago
Try adding `--new-instance` or `--no-remote` to your invocation.
284.
by callahad 7y ago
We also have some developer-focused release notes at https://hacks.mozilla.org/2019/07/firefox-68-bigints-contras... But more than anything... BigInt! Finally! JavaScript has real integers on Chrome and Firefox no
285.
by callahad 7y ago
...and since parent was specifically referring to ebooks: - Harry Potter and the Philosopher's Stone is not available for purchase in the US: https://play.google.com/store/books/details/J_K_Rowling_Harr..
286.
by callahad 7y ago
Fwiw, Google Play does have regional stores. For example, https://play.google.com/store/apps/details?id=com.hutchison3... is only available in the UK store.
287.
by callahad 7y ago
It looks like that should have been resolved a month ago with build 1.0.1921 ( https://github.com/mozilla-mobile/fenix/issues/2252 )... are you sure your bookmarks are set to sync (check in about:preferences on
288.
by callahad 7y ago
I understand where you're coming from, but I honestly find Firefox Preview's built-in tracking protection blocks enough ads on its own. I'd encourage you to give it a shot. (Though, to reassure you: proper adblocking is on
289.
by callahad 7y ago
Not a typo; we had not formally announced that Focus was on hold while we bootstrap the Firefox Preview / GeckoView / Mozilla Android Components ecosystem. Now we have. :) If you're interested in community maintainership of
290.
by callahad 7y ago
Not really. The project leaders have explicitly stated that the content of the script at that URL is subject to change at any time, and thus users are prohibited from locking it to an audited, known version with an SRI hash.
291.
by callahad 7y ago
It is impossible to use AMP as a standalone Custom Element library and still validate as AMP. Valid AMP is required to dynamically load the library from Google's unversioned CDN.
292.
by callahad 7y ago
Don't forget Let's Encrypt!
293.
by callahad 7y ago
Interesting to compare this to the Hello World that's now possible with WASI and its fd_write function: https://github.com/CraneStation/wasmtime/blob/e530a582afe6a2...
294.
by callahad 7y ago
Is that plausible? I thought MongoDB was the only major, industrially successful AGPL project, and they relicensed last year to SSPL.
295.
by callahad 7y ago
I should really write a script to generate this from MDN's browser compatibility data ( https://github.com/mdn/browser-compat-data ), but many APIs aimed at making browsers more competitive with native apps tend to
296.
by callahad 7y ago
It makes a huge difference in support for web standards. There are many nice things that Firefox supports which Webkit does not. It also means that we have to lobby Apple to support standards, since we're not allowed to compete on meri
297.
by callahad 7y ago
Does anything seem amiss at https://www.youtube.com/html5 ?
298.
by callahad 7y ago
Only Strings are safe, forty years past K&R. Wish I knew Tcl.
299.
by callahad 7y ago
You can define a toJSON property on the BigInt prototype that gets used for serialization: Object.defineProperty(BigInt.prototype, "toJSON", { get() { "use strict"; return () => S
300.
by callahad 7y ago
> Am I interpreting this correctly? Not quite. In the normal case, users will never see any difference as a result of this change. Most users will experience it, semantically, as "profile per channel," separating normal Fir

More ›