I just wish they had a restore feature like chrome does.
On firefox, once you close gracefully, there doesn't seem to restore the whole previous session without using an extension.
Firefox has lots of room to improve if it wants to beat Chrome
241–250 of 401 posts
Re: Firefox has lots of room to improve if it wants to beat Chrome
#242Earlier quoted context omitted.
>> that little "want a better browser" pop-up displayed on Google's search engine? I actually do not know what you're talking about. Been using Firefox for the last few years and haven't seen this pop-up once.
As another Firefox user, I know the pop up very well. Not even the results page where people at distracted, it's on the actual Google homepage (as well as other places). Abusing monopoly in one market to monopolize another.
Is it possible that this is somehow forbidden by EU law, that's why me, being EU citizen, never encountered it?
Re: Firefox has lots of room to improve if it wants to beat Chrome
#243Earlier quoted context omitted.
As another Firefox user, I know the pop up very well. Not even the results page where people at distracted, it's on the actual Google homepage (as well as other places). Abusing monopoly in one market to monopolize another.
Is it possible that this is somehow forbidden by EU law, that's why me, being EU citizen, never encountered it?
running an adblocker?
Re: Firefox has lots of room to improve if it wants to beat Chrome
#244Last week, a Brave browser developer documented the first-time startup phase of the competition through the eyes of a packet analyzer in a "What Happens.."-Series. Of the ones inspected, "Firefox [was] one of the most active upon installation." and ".. the only one to immediately collect telemetry data too"[^1].
Reading through his findings in detail and others responses - and what is read in this article I do not find much issue in the aggregate: bringing attention to nitpicks through bugtrackers, an organisation has the opportunity to make a concerted housekeeping effort to streamline the onboarding again. It is customary for websites and software to accumulate cruft over time from different internal teams with different goals. So it is best to turn to the bugtrackers, gently raising awareness with descriptive and good issue tickets.
[1]: https://twitter.com/jonathansampson/status/11658588961766604...
Re: Firefox has lots of room to improve if it wants to beat Chrome
#245Everyone's talking about what Firefox should do to beat chrome, and meanwhile here I am still suffering the bug that makes it unusable for many MacBooks with retina screens set to "more space". Start Firefox and fans are blaring in seconds, hundreds of reports, years of waiting and no solution... Maybe making it usable in one of the most common devices for devs would be a start, I've got a full building of coworkers…
Yep this is the ONE thing that kills FF for me. I use an external 4K display (via Display Port) on a 2015 15 inch MacBook Pro and Firefox basically just spins the fans up nonstop while it is running.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#246I would much rather use Firefox full time, but many sites (like youtube.com, for example) just don't render well/speedily/at all on FF.
Open Chrome and everything is fine. I get TFA said some devs don't write/test for anything but Chrome... but you _have_ to keep Chrome around for some things.
So much for an open web. ¯\_(ツ)_/¯
Re: Firefox has lots of room to improve if it wants to beat Chrome
#247> While I understand that they have to make money somehow I don't. I don't understand how Mozilla has over a thousand employees and over 500 million dollars in annual revenue. With that kind of money, Firefox should be absolutely dominating the browser space. They shouldn't be making Firefox worse with advertising in order to subsidize their flailing around trying to find traction in mobile or VR. It actually reminds…
No, the whole point of Mozilla is to "ensure the Internet is a global public resource, open and accessible to all." https://www.mozilla.org/en-US/mission/ Firefox, Thunderbird, and other projects are a means to that end.
Well I was there when Firefox was born (i even sent a donation and got the CD). To me these “corporate missions” are just marketing fluff. Just give me the browser.
Re: Firefox has lots of room to improve if it wants to beat Chrome
#248Earlier quoted context omitted.
> As a full-time firefox user, I commonly find that sites have bugs, and when I boot it up in Chrome just to check my hunch, they don't manifest. Also a full-time Firefox user. This is fascinating because I quite literally cannot remember a website for which I had to switch browser so it would start working. What kind of websites are these? Have you noticed any pattern about them? Perhaps it's a certain type of site…
For instance, my bank (Lloyds) has a login screen where you have to select letters from three long drop down lists containing all letters and numbers. With Safari or Chrome, I can select the dropdown (by clicking it or navigating there using the keyboard) and then enter the letter or number on the keyboard. With Firefox, I have to click on the dropdown, scroll down looking for the right letter/number and then select…
As inconvenient as powering through this bug might be, switching to Chrome to use this site just reinforces their choice. Perhaps emailing them to report the issue might also be beneficial for all?
Re: Firefox has lots of room to improve if it wants to beat Chrome
#249Earlier quoted context omitted.
I use Firefox on Linux and (current) Edge on Windows, in both cases because they feel faster than Chrome (which I used to use when it felt faster). I still use Chrome on my phone because I can't uninstall it. :)
You should be able to disable system packaged apps unless you are running an absolutely ancient version of Android. It's the same effect as uninstalling except it keeps the original package in storage in case you re-enable. Firefox on Linux doesn't have GPU acceleration out of the box nor GPU video decoding (at all still?). Firefox on Android has it's own litany of issues (though to be fixed in their new version soon…
Exactly, disabled apps still take up space. So on a limited space device I just use what's there.
I haven't tried the new version of Edge based on Chromium, but my guess is that it'll be as slow as Chrome. :(
Re: Firefox has lots of room to improve if it wants to beat Chrome
#250Earlier quoted context omitted.
I think it's some sort of anti-keylogger pattern that Lloyds are using. The select options all look like this: c I suspect the nbsp is what blocks the usual keyboard behaviour on Firefox but not on Chrome. This is quite strange, because it could mean that the anti-keylogger feature only works as intended with Firefox but not with Chrome.
Interesting, that could be something not too complicated to change on Firefox, I'll try to contribute when I'll have a bit more time. At least that's the first time I see something I could realistically improve.
I'm not sure whether Firefox should actually be changed. It looks like Firefox may be conforming to the standard and Lloyds devs may have intended to use that standardised behaviour to thwart keyloggers.
Only they seem to have forgotten to test whether it actually does block keyloggers, and it only does so in Firefox.
So my grand example for a website not working well in Firefox may be just the opposite - Firefox saving my money from getting siphoned off by thiefs. Very bad choice of example on my part! :-)
Here's what the HTML 5 spec says on the element's text content:
The text IDL attribute, on getting, must return the result of stripping and collapsing ASCII whitespace from the concatenation of data of all the Text node descendants of the option element, in tree order, excluding any that are descendants of descendants of the option element that are themselves script or SVG script elements.
https://html.spec.whatwg.org/multipage/form-elements.html#th...
nbsp is not ASCII whitespace and so it should not be stripped. I can't seem to find anything specific on the autocomplete behaviour in this case, but arguably autocomplete should use the text content without further normalisation. Perhaps this is where Chrome and Safari devs would disagree.
In any event, this raises a bigger question. What if a site is actually broken in Firefox, but it's not Firefox's fault? Should Firefox then be changed to non-conforming behaviour, aping any Chrome bugs? That would put a huge question mark on all the work they put into making their own rendering engine instead of just using Blink.