• 3 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • But if you’re using the built-in auto-updater (like people tend to do on Windows and macOS), then it happens automatically in the background, unless you tell the auto-updater to not update automatically.

    Definitely does not work that way on my Windows 10 installation. When update is available, Firefox will have a “Restart to install updates” in menu button notification - but the files are not replaced on disk until you actually close (or restart) Firefox and thus Firefox continues to work normally.

    What can happen though is that if you run another instance (ie. another profile) of Firefox while the first one has “staged” the update then that another instance can trigger the files to actually be replaced on disk but you would very deliberately do that.


  • Firefox shouldn’t force you to restart and update like that unless something else, such as your package manager, has already replaced the executable files on your disk. In such a scenario Firefox doesn’t have any option except to inform you to restart it (well I guess it could choose to crash). But the mechanism that forced the update is the package manager.


  • The non-standard :-moz-lwtheme is now considered invalid syntax, so using that invalidates the whole ruleset it’s used in. Featurewise the equivalent would be to check for existense of lwtheme attribute on root element. But the way you have written your rules the you have never even needed :-moz-lwtheme selector to begin with since you are applying the same rules when that matches and doesn’t match. So you can just write this to get your desired selection color in urlbar:

    #urlbar ::-moz-selection{
      background-color: #3040cf !important; /*it's green again; want to fix this too*/
      color: white !important;
    }
    





  • That’s not necessarily a good solution either, because a service could figure out that the source of random fingerprint data likely comes from the same user. Especially if your ip is not changing. It might perhaps be effective if a substantial amount of people were doing it though.

    But to generate such random fingerprint is difficult because it consists of many parts and services don’t all build fingerprints the aame way. You could easily randomize e.g. canvas data, but the issue is that if you only randomize one data point then that one random data point pretty uniquely identifies you if your other datapoints are stable. So to be effective you would really need to randomize several different datapoints and that may not be such an easy task since websites could build them in all sorts of ways.




  • Indeed. I mean, I’m blocking ads as much the next guy and that’s not going to change in any foreseeable future, but I cannot see how introduction of privacy preserving advertising platform could possibly be seen as anything other than an improvement over the current, completely perverse, situation. It would be better for people who don’t block ads, so if this acquisition would advance uses of privacy-respecting advertising systems and simultaneously get some revenue to Mozilla then this sounds quite like a win-win to me.



  • MrOtherGuy@lemmy.worldtoFirefox CSS@lemmy.worldis CSSs safe?
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 months ago

    Yeah, loading any external resources - I would think fonts even more so than images - is potentially risky. In addition, there is somewhat realistic possibility for browser fingerprinting if you use some style that makes browser viewport size atypical.

    I can’t think of any actual security issues other than those. Otherwise the worst that a style could do is crash the browser, to make it utterly unusable or make it super slow. But those are all recoverable by simply trashing userChrome.css and restarting Firefox.







  • I mean, there are options. It could mute/unmute, close the stream, copy one of various track information such as track name or playback position, send the video to different screen etc. But I can’t think of anything that makes much sense, although mute/unmute is at least somewhat sensible.

    But, yeah, it’s one of those interactions that has just always worked like that, long before browsers could play video even. It’s similar to how Ctrl+C copies stuff, Ctrl+Z undoes previous operation, right-click opens a context menu etc.; they don’t have to do those things, but users have learned to expect it, so it would be pretty dumb to change that with no reason.