Whenever I say that I use Chrome on my android phone, some smart troll retorts with "But why not Firefox?"
The truth is that I tried to use Firefox many times on Android. It is these little things like this nagging bug[1] that push me back towards Chrome.
This is a five years old bug, you can see my own comment [2]. Firefox still doesn't have even as basic a feature as spell check on the text editors in the browser window! There are two options apparently, they can either use Hunspell package (which increases the app's download size a bit) or the Android's built-in spell checker. In all these five years, Mozilla is still unable to decide which of these two methods to use and the bug remains unresolved as of now (face palm!).
I hope this (and other similar nagging issues) get resolved soon and Firefox becomes usable on mobile. Next time, please don't ask why I use Chrome!
After many years of using Google Chrome I switched to Firefox due to privacy concerns. Overall I've loved the experience so far, but there's one thing that bugs me: the suggestions. Firefox seems to be unable to make a sensible use of my browsing history. It suggests urls I visit only very rarely, or sometimes even suggests things I've never visited (I read some time ago that they would start providing sponsored suggestions). For example, it's completely clueless about my Reddit browsing habits. The only subreddit I visit most of the time is r/rust, but it doesn't appear in FF's suggestions. There's only reddit main page, which I have never consciously visited. Sometimes the problem is the opposite - I want FF to suggest a url of a main page of, for example, a blog, but what I get are only some random posts I read on that blog a long time ago. Initially I thought that was a bug which would get fixed in a subsequent release, but this situation has been going on for at least a few months. Chrome's suggestions were way more intuitive for me.
I protected my Microsoft account with 2-factor authentication using Google Authenticator for perhaps 2 years. Until 27 October 2018, if I logged into outlook.com or onedrive.live.com, I would be prompted for user ID, password, and a token from Google Authenticator. On 27 October 2018, I made a change. I removed 2-factor authentication from my account, only to immediately add 2-factor authentication right back on with Google Authenticator and 1Password OTP. The two code generators are in sync.
Since 28 October 2018, when I log into outlook.com or onedrive.live.com, I am NOT prompted to provide a one time code. The only time I am prompted to provide a code in the Microsoft environment is when I enter the MS account security page. This does not seem like correct behavior, having only the account security page of the overall MS cloud computing environment 2fa protected, but leaving email and documents unprotected. Nor does this new behavior match prior behavior before the change on 27 October 2018.
I have full control over my account at this time.
I have been able to replicate this behavior across 3 browsers (Firefox, Chrome, and Safari. Note Safari is a naked browser with no add-ins) and the incorrect behavior persists since 28 October.
I submitted the bug report to Microsoft Security Response Center <secure@microsoft.com>, who acknowledge it seemed like a bug but closed the issue on their end without taking action. They asked if the issue persists to resubmit with a bunch of stuff that is way outside my wheelhouse.
* Description of the vulnerability
Detailed steps required to consistently reproduce the issue
Short explanation on how an attacker could use the information to exploit another user remotely
* Proof-of-concept (POC), such as relevant code samples, a video recording, crash reports, or screenshots
Does anybody know a person in Microsoft who might be willing to take this up?
Simultaneous spell checking of multiple languages is a feature available in Google Chrome web browser form a long time. There is such feature request for Mozilla Firefox web browser also from a long time. But it is still not implemented. There are several related open issues in the Mozilla's bug tracker:
Despite the fact that the oldest of them is more than 19 years old, no real progress is made. Manual language switching is required and this is a usability nightmare for everyone who uses a more than one language simultaneously. For example, for me is a common practice to write messages in my native language and to mix English terms in them. The lack of this feature is the main reason for me switching back to Chrome, after I had returned to Firefox when Firefox Quantum was released. I suspect that only the lack of this feature is the main reason for many other people to not use Mozilla's browser and that this is a huge damage on their user base.
After all, for the feature to work the same way as in Chrome, does not look very difficult. The algorithm can be simply:
function check(word, active_dictionaries): for dictionary in active_dictionaries: if word in dictionary: return true return false
Of course there can be some complications related to Firefox internals, which do not allow such a simple implementation, but 19 years are really a long time. I suspect that the reasons this not happen until know are not technical, but purely political?
Hello HN, I am building a devtool to understand existing codebases. The idea originates from my time at big tech as well as various attempts to get involved in open source projects.
When I was in college I wanted to improve my coding skills by contributing to opensource projects. I would pickup a bug or feature request but I always found myself stuck at the very first step. I did not understood where and how to begin contributing. I once submitted a patch in firefox which was labeled "Good first issue" but that was still very handheld. The assigner told me exactly which files I need to update and what changes are needed. It took me a week to push the patch. But I didn't feel good about it because the guy could have done the same task himself in 10 minutes and he had to spend significantly more time telling me to what to do. Then for years, I made very few contributions and that too where I knew how the project is organized by working on it as part of my day job.
I found similar issue while working at Amazon. Very often you need to work on projects handled by other teams or code which are not being maintained. And the problem boils down to where do I even begin. Which components are responsible for what. Once you understand that, it is significantly easier to figure out what needs to be done. Plus many big tech companies follow something called bus factor. The logic goes like like this: if one of the team mate is hit by a bus the development of the project should not stall. So you need to abandon project which you just understood well. So you often end working on new codebase all the time.
Lucid code is my attempt to solve this problem. It helps you quickly figure out which parts of code are responsible for what. To test the utility of my tool, I decided to contribute to an opensource project which I was not familiar with and see how long that takes. I choose manim to do so. I was able to get a high level overview of the codebase in couple of hours. And I was able to create a custom animation in another hour or so. Biggest help I found was that at no point I was completely lost.
As of now, the tool is not so good that helping you bug fixes as a lot of bugs are situational error(xyz happens when the value of abc is 123 etc). These are more suited to setting up the environment, firing up the debugger and reproducing the bug. But I have plans to extend tool to help in this kind of situation as well.
I would love to get your feedback and suggestions. You can try the tool for free without the need of a signup. Please try it and let me know here or at pushpankar@lucidcode.ai.
Ran in to this for the 2nd time recently. Is firefox the new browser to work around? It's been working properly in IE for years.
Clear example: http://jsfiddle.net/YjHaB/9/
How is it that some bugs go neglected for this long?