dblohm7

74 ms·

781.
by dblohm7 9y ago
about:memory will help you there. Save those reports (you can even anonymize them) and include them in a bug report.
782.
by dblohm7 9y ago
FWIW, developer edition is now the Beta channel.
783.
by dblohm7 9y ago
We're already at that point IMHO.
784.
by dblohm7 9y ago
Firefox now includes many rust components.
785.
by dblohm7 9y ago
It hit during my last final exam of the summer term. We were lucky that our prof let us complete the remainder of our exam under the glow of emergency lighting.
786.
by dblohm7 9y ago
Perhaps you should use Developer Edition instead? It uses a separate profile.
787.
by dblohm7 9y ago
Don't forget the huge perf improvements to session restore!
788.
Firefox 54 Release Notes(mozilla.org)
95 points by dblohm7 9y ago|1 comments
789.
by dblohm7 9y ago
AFAICT the only reason is that you need it for compatibility. If your variant and version fields aren't valid, you don't have a UUID anymore -- you have something else.
790.
by dblohm7 9y ago
> I want the open web to flourish. When the open web wins, Mozilla wins.
791.
by dblohm7 9y ago
Report those broken websites to webcompat.com
792.
by dblohm7 9y ago
It might be worth reporting this on webcompat.com
793.
by dblohm7 9y ago
There's a lot of FUD about this, though. https://feeding.cloud.geek.nz/posts/how-safe-browsing-works-...
794.
by dblohm7 9y ago
You can report issues like this to webcompat.com
795.
by dblohm7 9y ago
Your evidence is very much anecdotal.
796.
by dblohm7 10y ago
Quantum is the umbrella, if you will, under which a bunch of performance focused subprojects are being developed. Some of them (Quantum Render, Quantum CSS) are importing Servo components (WebRender and Stylo, respectively), while others (Q
797.
by dblohm7 10y ago
Hard to say. Clearly there are two camps. While we are indeed forcing an abstraction layer onto extension devs, that does not necessarily mean that we are going to use Chrome as the lowest common denominator with respect to extensibility. H
798.
by dblohm7 10y ago
Nope, they're referring to a new UI called Photon.
799.
by dblohm7 10y ago
A reminder that Quantum is the name of the project, not the engine. The result of Quantum is still Gecko.
800.
by dblohm7 10y ago
Yeah, I think our big bet here is that Firefox will achieve better market share by leapfrogging the competition in performance versus remaining insanely customizable despite lower performance. EDIT: Added "insanely"
801.
by dblohm7 10y ago
100% agreed
802.
by dblohm7 10y ago
That's Quantum Render, not Quantum Compositor.
803.
by dblohm7 10y ago
mccr8 is a Mozilla engineer.
804.
by dblohm7 10y ago
The Firefox bug was trivial to fix, but nobody at Google bothered to report it. If they had, it would have been a non-issue by the time that Inbox was released.
805.
by dblohm7 10y ago
Correct.
806.
by dblohm7 10y ago
Correct. The Web API is standardized, but how the engine interfaces with the actual content decryption modules is not.
807.
by dblohm7 10y ago
That's why. 64-bit touch multiprocess isn't ready until v54.
808.
by dblohm7 10y ago
I'm the developer responsible for multiprocess on touch screens. There was a mixup in the release notes. This is what the realities of the situation are: Touchscreen Windows users running 32-bit Firefox 52 should have multiprocess. Tou
809.
by dblohm7 10y ago
I believe that is Oracle's official recommendation for dealing with NPAPI deprecation.
810.
by dblohm7 10y ago
Are you running a 64-bit build of Firefox, by any chance?

More ›