On 07/11/2014 10:12, Marco Bonardo wrote:
On 07/11/2014 10:40, Gijs Kruitbosch wrote:
Where can we read about how this decision was made? On my profiles with
Force RTL, e10s perma-crashes (
https://bugzilla.mozilla.org/show_bug.cgi?id=1072980 ), and in most
other cases, I only ever see spinners for remote content (ie can't
actually browse the web - doesn't matter too much for me because I
normally use beta).
I recognize that my experience is not universal, but I hope it makes
sense that I'm... surprised... that we're turning this on for everyone.
FWIW, my experience is pretty similar to yours.
I'm forcing myself to use it for everyday work, but I completely dropped
forceRTL and Flash (I must admit I'm not missing it) to make it usable.
Sometimes it is hanging for seconds (white content in every tab) and the
content process is crashing often. But in the end, it's usable.
Right, it's that last part that is very much not the case for me.
I looked for a bug for a while and decided to just file one:
https://bugzilla.mozilla.org/show_bug.cgi?id=1095407
Nightly is for testing bleeding edge features and make them ready for
prime time. We just got too much acquainted to a stable Nightly and that
was not its scope, it was called Minefield for a reason.
I'm happy we are enabling e10s for nightly testers if that allows it to
improve faster, regardless of its status.
Maybe, but if we break people's browsers too badly for too long, I
expect they'll just go back to more stable channels and/or
$OTHERBROWSER, which defeats the point. There's a tradeoff here, and I'm
interested as to what data/reasoning we used to decide what we did.
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
