[-] MrOtherGuy@lemmy.world 12 points 1 month ago

Doesn't really sound like a company that I would want to do any business with then.

[-] MrOtherGuy@lemmy.world 17 points 1 month ago

Also, Servo was originally more or less a testbed for new rendering pathway (webrender) which, when ready, was then integrated into Firefox.

[-] MrOtherGuy@lemmy.world 13 points 2 months ago

Indeed. Also, the auto-open PiP is super nice feature I've been using a lot.

[-] MrOtherGuy@lemmy.world 14 points 4 months ago

Well the feature development is certainly progressing - here is the tracking bug for it.

You can nowadays just test it in normal nightly without special build - it's extremely incomplete, but you can test it if you wish. It's tied to revorked sidebar which you need to enable in about:config.

[-] MrOtherGuy@lemmy.world 52 points 4 months ago

Absolutely not. If anything, public officials would be the one group whose messaging I would understand being scanned so that the people can sort of keep them on check. But again, implementing such possibility that would still weaken security of everyone else as well so of course it should not actually be done.

[-] MrOtherGuy@lemmy.world 20 points 6 months ago

Yes. I want to have access to both history and bookmarks on all my devices and send specific tabs to other devices. Sync makes these super convenient.

21
submitted 7 months ago by MrOtherGuy@lemmy.world to c/firefox@lemmy.ml
[-] MrOtherGuy@lemmy.world 21 points 8 months ago

Right, but then you shouldn't be shocked to find out that a feature was removed because nobody seemed to be using it.

[-] MrOtherGuy@lemmy.world 18 points 8 months ago

My first guess would be that this is caused by the website implementing its own navigation/history behavior using History API. That can easily mess things up, or at least not behave like you might want.

[-] MrOtherGuy@lemmy.world 33 points 10 months ago* (last edited 10 months ago)

If a website has a compatible PWA manifest the there will be an item labelled "install" in the three-dot menu of Firefox in place of usual "add to homescreen" item.

Edit: There's a few other requirements as well for the website to be considered installable as PWA, such as it must have a registered service worker so it can work offline. But regardless, if the website provides all the requirements then it can just be installed straight from the menu.

[-] MrOtherGuy@lemmy.world 53 points 10 months ago

Unfortunately by sending DNT you are merely suggesting to the server that you wish to not be tracked. There's no requirement for the server to actually care about you at all.

Now, if DNT were actually legally binding though - that would indeed be very cool.

[-] MrOtherGuy@lemmy.world 24 points 1 year ago

None.

I don't think it's a good idea to take some huge collection of prefs and just apply them blindly.

Instead, make the changes that you actually want to do, so that you actually know what changes you are causing. If you want to put those into your user.js file then feel free, but in my opinion it's just better to change them in about:config directly - that is, unless you need to apply the exact same set of changes to multiple profiles.

[-] MrOtherGuy@lemmy.world 16 points 1 year ago

Also, mobile Firefox has supported PWAs for a long time. I wouldn't say PWAs on desktop would be useless, but they make much more sense on mobile than on desktop.

1

Hi! Just FYI folks, the plan going forward would be to build this community on Fedia instead: Right here https://fedia.io/m/FirefoxCSS

Thanks to federation, you can also participate in the community through lemmy if you want - though some features such as microblog or sidebar info won't be accessible via lemmy - for now at least. The link to access the community via lemmy world would be https://lemmy.world/c/FirefoxCSS@fedia.io

See ya there!

1
submitted 1 year ago* (last edited 1 year ago) by MrOtherGuy@lemmy.world to c/firefoxcss@lemmy.world

Perhaps not fitting exactly for this community because it's about a website, but hey c'mon its customizing :) Apply via userContent.css or Stylus or something.

Only tested with "darkly-red" style that you can select from your user settings.

1

Let's have this post here also...

As a part of the front-end technical modernization the old xul box model is being replaced with modern flexbox all around the UI. Relevant bug 1820534

Previously, just about everything used display: -moz-box but in Firefox 113 the default display model was changed to modern display: flex instead.

What this means first-hand is that all legacy box model -related properties will not do anything anymore so things like -moz-box-ordinal-group, -moz-box-orient, -moz-box-direction, -moz-box-align, -moz-box-pack or -moz-box-flex won't have any effect.

The suggested way to deal with this is to just update your styles to use equivalent flexbox properties. Additionally, the old display: -moz-box is treated as invalid property value

Some examples of conversions:

  • display: -moz-box -> display: flex
  • -moz-box-ordinal-group: 0 -> order: -1
  • -moz-box-orient: vertical -> flex-direction: column
  • -moz-box-direction: reverse -> flex-direction: row-reverse
  • -moz-box-align: center -> align-content: center or align-items: center depending on what you are doing.
  • -moz-box-pack: start -> justify-content: flex-start or justify-items: flex-start
  • -moz-box-flex: 10 -> flex-grow: 10

Notes about order vs. -moz-box-ordinal-group: order supports negative values, whereas ordinal-group does not. Default value of order is 0 but default of ordinal-group is 1 so you might need to change what value to apply for it to have any effect.

Also, see this firefox-dev post for more information.

view more: next ›

MrOtherGuy

joined 1 year ago