emiliocobos

4 ms·

1. 1.▲
   by emiliocobos 1y ago

   Xul would've had the same issues.
2. 2.▲
   by emiliocobos 5y ago

   To people thinking that this was removed gratuitously please read the bug and linked bugs carefully. This got in the way of implementing various improvements to <meta charset> and interop improvements to XHR.
3. 3.▲
   by emiliocobos 6y ago

   Bobby (the Mozilla rep) was also heavily involved with Servo and Rust-in-Firefox, see e.g. https://bholley.net/blog/2017/stylo.html
4. 4.▲
   by emiliocobos 6y ago

   A bit of extra context from looking at blame: * It seems Google Location Services has been the default location provider since a long long time ago (probably since before the Mozilla service existed). * It seems like Firefox uses system API
5. 5.▲
   by emiliocobos 9y ago

   The STR for that bug are in comment 3, but I can try to get something better when I'm back home (on my phone now). We get significant speed ups from parallelism and such on big doms over all during page load, but we also get speedups f
6. 6.▲
   by emiliocobos 9y ago

   (for more context, Facebook has a very small style recalc time, so we're bottlenecked right now on the time it takes for us to parse CSS, and build the data structures for selector-matching and invalidation, and the patches on the queu