4 ms·

Agree about Mozilla's engineering culture, in their mobile division at least. It's startling to think that literally the only alternative to a Blink monoculture

Agree about Mozilla's engineering culture, in their mobile division at least. It's startling to think that literally the only alternative to a Blink monoculture on Android is a poorly-managed alternative. I now see myself as a holdout of Firefox on desktop, because the constant issues and quagmire of inexplicable UI changes compelled me to move to Brave on mobile. As an example, the GeckoView ticket[1] that #17716 depends on has been constantly pushed back from v88 to possibly v93 or later over the past year. Being able to save an image that I am able to see on a webpage is what I consider basic functionality, but there does not seem to be much of an acknowledgement from the GeckoView team about its importance. Another example is this[2] issue report I submitted. It was closed because they "couldn't address it", and even after providing a video showing the exact problem, my report was still ignored. The issue is that it does not matter whether or not they consider it a problem, because I do, and Chromium does not have the same problem. That only makes me more likely to choose Chromium over Firefox. Compound that a dozen times over, and for me, practicality wins out over principle. I'm also worried about the long-term stability of their mobile division - not only because of Servo, but because issues related to the mobile team being understaffed and overworked had come to light in at least once instance in the past. Mobile web browsers are becoming far too important to get wrong in the present day, and after realizing this fact, I have to wonder why Mozilla's financial structure still prevents direct contributions to their development teams for Firefox, and why they are still using what resources they do have on far less important projects like Mozilla VPN or Relay. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1690037 https://bugzilla.mozilla.org/show_bug.cgi?id=1690037 [2] https://github.com/mozilla-mobile/fenix/issues/17525 https://github.com/mozilla-mobile/fenix/issues/17525

nyanpasu64 5y ago
I saw your previous post at https://news.ycombinator.com/item?id=28495622 https://news.ycombinator.com/item?id=28495622: > Scrolling up inside an input box while the page is at the top of the screen causes unintentional pull-to-refresh I saw this too, has it been reported? > Most recently visited page is not restored when closing and reopening the app, even though it's saved to the history (closed as wontfix) What's the issue URL? I want to read the history and maybe complain too.
- nonbirithm 5y ago
  > I saw this too, has it been reported? I believe it was fixed a while ago, but I had pull to refresh disabled as a workaround at the time (when they finally made it configurable). The pull-to-refresh implementation is a prime example of a buggy feature that was pushed out too early and only underwent sufficent testing only after it reached users. Some of the issues stemming from it still weren't fixed even a year afterwards, and they appeared in places as critical as Google's search results page. https://github.com/mozilla-mobile/fenix/issues/9766 https://github.com/mozilla-mobile/fenix/issues/9766 > What's the issue URL? I want to read the history and maybe complain too. It's the GitHub link in my previous comment.
  - nyanpasu64 5y ago
    Pull to refresh is not fixed; test at https://tasvideos.mistflux.net/ https://tasvideos.mistflux.net/.
    - nyanpasu64 5y ago
      In any case, I reported it at https://github.com/mozilla-mobile/fenix/issues/21405 https://github.com/mozilla-mobile/fenix/issues/21405.
  - nyanpasu64 5y ago
    > The pull-to-refresh implementation is a prime example of a buggy feature that was pushed out too early and only underwent sufficent testing only after it reached users. I found out that this may not be accurate. Looking at https://github.com/mozilla-mobile/fenix/issues/21175 https://github.com/mozilla-mobile/fenix/issues/21175, pull-to-refresh is simply absent from release builds, and only present in nightly builds. I wish it worked properly there though.

nyanpasu64 5y ago

I saw your previous post at https://news.ycombinator.com/item?id=28495622 https://news.ycombinator.com/item?id=28495622: > Scrolling up inside an input box while the page is at the top of the screen causes unintentional pull-to-refresh I saw this too, has it been reported? > Most recently visited page is not restored when closing and reopening the app, even though it's saved to the history (closed as wontfix) What's the issue URL? I want to read the history and maybe complain too.

nonbirithm 5y ago
> I saw this too, has it been reported? I believe it was fixed a while ago, but I had pull to refresh disabled as a workaround at the time (when they finally made it configurable). The pull-to-refresh implementation is a prime example of a buggy feature that was pushed out too early and only underwent sufficent testing only after it reached users. Some of the issues stemming from it still weren't fixed even a year afterwards, and they appeared in places as critical as Google's search results page. https://github.com/mozilla-mobile/fenix/issues/9766 https://github.com/mozilla-mobile/fenix/issues/9766 > What's the issue URL? I want to read the history and maybe complain too. It's the GitHub link in my previous comment.
- nyanpasu64 5y ago
  Pull to refresh is not fixed; test at https://tasvideos.mistflux.net/ https://tasvideos.mistflux.net/.
  - nyanpasu64 5y ago
    In any case, I reported it at https://github.com/mozilla-mobile/fenix/issues/21405 https://github.com/mozilla-mobile/fenix/issues/21405.
- nyanpasu64 5y ago
  > The pull-to-refresh implementation is a prime example of a buggy feature that was pushed out too early and only underwent sufficent testing only after it reached users. I found out that this may not be accurate. Looking at https://github.com/mozilla-mobile/fenix/issues/21175 https://github.com/mozilla-mobile/fenix/issues/21175, pull-to-refresh is simply absent from release builds, and only present in nightly builds. I wish it worked properly there though.