3 ms·

Most of those bugs were in font rendering.

• sneak 6y ago
  I saw; such a security-focused browser would naturally use only local, trusted fonts and strongly sandbox media playback/decode of any kind, probably in a different process. We need slow and safe before we can have fast and safe. Either is better than the fast and unsafe we have now. We should probably unfuck the dangerous morass that is turing-complete font file formats at some point, too.
  • floatboth 6y ago
    Firefox at least uses the wasm sandbox for Graphite, the really fancy turing-complete font thing: https://hacks.mozilla.org/2020/02/securing-firefox-with-webassembly/ https://hacks.mozilla.org/2020/02/securing-firefox-with-weba... Same with Ogg container parsing.
  • novok 6y ago
    The direction of webdev is webasm delivering full almost-desktop level apps and SPAs vs the documents with some minor scripting of the past. Slow & safe javascript will simply not be adopted by the market because there is zero incentive to do so. Change the incentives and you will get the change you want.