dao- · HackerTrans

12 माह पहलेdiscuss

Drop the hyperbole for a second. It was a choice screen, a far cry from force-feeding. I'll grant you, somewhat wide adoption is almost a given when putting this kind of UI in front of all users, but that still doesn't mean that it was a mistake or a net loss to give folks who wouldn't normally customize Firefox a chance to do so. So, what's your point?

dao-

12 माह पहलेdiscuss

> How much public opinion is worth burning for how much increased usage of a new theme feature? In my opinion, very little.

I think we're squarely in the "very little" range here in terms of how much public backlash we saw. You might be overestimating how widely folks got angry the same way you got angry, or perhaps we weren't monitoring the right forums and channels when releasing the feature, who knows.

dao-

12 माह पहलेdiscuss

There's for sure a lesson to be learned in here. The product owner who had decided and pushed for making it seem like colorways were ephemeral has long left Mozilla, so you're preaching to the choir at this point.

I still don't consider colorways a failure, all things considered. To me, the fact that colorways are still some of the most used themes outweighs you remembering that you were angry three or so years ago, but thanks for the feedback.

dao-

12 माह पहलेdiscuss

> People using colorways after the feature was removed? Well, that sounds like a failure of the feature then.

> The whole crux upon which the colorways marketing rested, was they were temporary! You get to change your theme for a few months, and then later on at some random point, it changes again as it's taken away from you.

It was sort of a marketing gimmick, one I wasn't particularly fond of. (I was the lead engineer for colorways.) What it really meant is that we'd offer the onboarding screen and colorways built into about:addons for a limited time. The intent was never to remove them once users installed them. We have since migrated them to AMO where they can still be installed: https://addons.mozilla.org/en-US/firefox/collections/4757633...

dao-

12 माह पहलेdiscuss

No, that had happened about two years earlier I think (https://bugzilla.mozilla.org/show_bug.cgi?id=1678742 goes back to 2020). Alas, the bottleneck there was UX staffing rather than engineering.

dao-

12 माह पहलेdiscuss

> Not surprising, since I believe Firefox gave everyone the Colorways screen when that feature showed up,

Right, I assume that's what the parent comment meant by "force-fed to us." That screen was indeed the whole point: It made the theming feature visible and accessible to the average users.

dao-

12 माह पहलेdiscuss

> Don't forget colorways, the non-feature that still needed to be force-fed to us. I assumed people who wanted to change the color theme already could

Most average users don't ever change settings or otherwise customize stuff, but that doesn't mean they wouldn't enjoy a different theme. Colorways saw good adoption according to our internal Telemetry. In fact, three years later colorway themes combined remain more popular than either Dark, Light, or Alpenglow, despite not being offered or advertised directly in Firefox anymore.

dao-

पिछला वर्षdiscuss

You could just set `browser.tabs.dragDrop.createGroup.delayMS` to a high value like 3000; that would mean having to rest the mouse for three seconds to group tabs during drag and drop.

dao-

पिछला वर्षdiscuss

In about:config, try looking for browser.tabs.dragDrop. The createGroup... and moveOverThresholdPercent flags control the group creation behavior during drag and drop. If anyone finds values that make it less likely to accidentally create groups while still allowing intentional grouping via drag and drop, I can channel these back to the team.

dao-

पिछला वर्षdiscuss

> Do you know how do you move a tab group once created?

It should work once you've updated to Firefox 138.

dao-

पिछला वर्षdiscuss

We've implemented drag and drop of groups for both horizontal and vertical in 138 which presumably you were updated to today :)

comments