mnoorenberghe
Re:More malicious extensions in Chrome Web Store
on Thursday June 01, 2023 @12:24AM (#36147556)
Google announced on December 9 that this timeline was paused: https://groups.google.com/a/chromium.org/g/chromium-extensio...
Re:Ask HN: Is anyone successfully self-hosting Firefox Sync?
on Monday February 06, 2023 @06:55AM (#34676137)
The functionality is (mostly) built into Firefox now so there’s little need for a separate app. You can enable native app autofill for both Android and iOS. There are a few things that should still be done to improve the experience but it doesn’t seem like a priority now.
Re:Password generator doesn't generate new password in the same session
on Tuesday December 20, 2022 @09:12AM (#34066123)
It uses a PRNG with no site-specific seed, it just stores that result temporarily so it can be filled it password confirmation fields or login forms during the same session to ensure the user can complete their password change process.
Code: https://searchfox.org/mozilla-central/rev/abcee8d2c97a5c8a1f...
Re:Password generator doesn't generate new password in the same session
on Tuesday December 20, 2022 @09:06AM (#34066037)
I believe you can right click in any type=password field to bring it up with the heuristics didn’t detect it as a new password field.
Re:Pausing Manifest V2 phase-out changes
on Sunday December 11, 2022 @08:57AM (#33943208)
Firefox and Safari are continuing to support HTML pages to run the background code in rather than forcing developers to use service workers with no DOM access.
Re:HTML attributes to improve your users' two factor authentication ex...
on Sunday January 12, 2020 @05:05AM (#22025475)
> You can use more than one autocomplete value at a time too. If your username is also an email address you can give the browser and any associated password managers a hint with ‘autocomplete="username email"’.
This whole paragraph is incorrect. While the attribute value does allow multiple tokens there is a very specific syntax defined in the HTML standard and it doesn’t support multiple field names (types) i.e. autocomplete="username email" is invalid. If you access ‘input.autocomplete’ on an input with that attribute value “” will be returned indicating this.
Re:Firefox 70
on Tuesday October 22, 2019 @01:50PM (#21326624)
This is incorrect AFAIK. The sync toggle for a data type is for the whole account, not per-device.
Re:Firefox 70
on Tuesday October 22, 2019 @01:49PM (#21326611)
Yes, it can now import logins/passwords from Chrome/Chromium on macOS, Windows support already existed for some years.
> Passwords can now be imported from Chrome on macOS in addition to existing support for Windows
Re:Issue 914451: Autofill does not respect autocomplete="off"
on Sunday October 13, 2019 @08:59AM (#21240131)
There are more than 20 different valid field name tokens in the spec, not just “on” and “off”[1]. If web developers actually used the other values correctly then user agents wouldn’t need to use heuristics to figure out the correct data to autofill.
[1] https://html.spec.whatwg.org/multipage/form-control-infrastr...
Re:Banks, Arbitrary Password Restrictions and Why They Don't Matter
on Wednesday September 18, 2019 @11:11PM (#21012906)
If you’re suggesting each subscriber gets a static IP then that’s much worse for privacy.
Re:Contributing to the Mozilla code base
on Friday August 02, 2019 @11:11AM (#20593561)
> Now they write this.
This page was written Apr 11, 2011
Re:Contributing to the Mozilla code base
on Friday August 02, 2019 @06:57AM (#20592012)
Are you on macOS or Linux? Passwords can be imported from Chrome/IE/Edge on Windows.
Re:Firefox to Warn When Saved Logins Are Found in Data Breaches
on Wednesday July 17, 2019 @01:01PM (#20461576)
Press reports that this is shipping in Fx69 were incorrect.
Re:Microsoft proves the critics right: We’re heading toward a Chrome-o...
on Wednesday March 13, 2019 @02:10PM (#19381632)
Reinstalling Firefox on a Mac is not the same as doing a Firefox Refresh. The former only touches the executable while the latter cleans up cruft in your Firefox data (potentially lingering around from legacy extensions).
Re:Ask HN: Mozilla Persona Post-Mortem
on Thursday January 18, 2018 @12:16AM (#16174881)
The after action report (AAR) can be found at https://wiki.mozilla.org/Identity/Persona_AAR
Re:Cellphone-Cancer Link Found in Government Study
on Friday May 27, 2016 @03:09AM (#11784415)
It's linked right in the article: http://biorxiv.org/content/biorxiv/early/2016/05/26/055699.f...
Re:Firefox 29
on Tuesday April 29, 2014 @03:30PM (#7669408)
Actually the page can only be notified when you type a certain message in the address bar and it's limited to ONE message in a browser window so it can't try to watch for a list of strings. When there is a match a new tab will open up so you would notice this if it was being used. This feature was intended for an easter egg so the page could say, for example, "let me know when the user types 'I love Firefox' in the address bar" and then open a tab with an easter egg page. Also note that all tour functionality only applies when the tour tab is selected. Hopefully this clarifies that the page can't really spy on the address bar.
Re:Firefox 29
on Tuesday April 29, 2014 @12:05PM (#7667905)
Hello, I'm one of the developers of the tour module on the Firefox team. The whitelist preference adds the whitelisted domains to the permission database when the application is upgrade to today's released (version 29) so changing the preference doesn't change the domains already whitelisted. You can disable the feature using the browser.uitour.enabled if for some reason this feature bothers you. Note that is also requires HTTPS for the whitelist domains too.