Open Bug 1709425 Opened 2 months ago Updated 1 day ago

[meta] Remove non-Proton branches from our CSS and JS, and Proton prefs

Categories

(Firefox :: General, task, P3)

Desktop
All
task

Tracking

()

Tracking Status
firefox89 --- wontfix
firefox90 --- affected

People

(Reporter: mconley, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [proton-cleanups])

Once Proton ships, we should remove the non-Proton branches in our CSS and JS that are no longer being used.

We can also then remove the Proton prefs and support for the the -moz-proton selectors.

Points: --- → 2
Priority: -- → P3

Could you please clarify when you plan to remove browser.proton.enabled which allows to enable (more or less) old style of the browser? Could you please consider keeping this option at least in the Firefox 91 ESR?

(In reply to Evgeny from comment #1)

Could you please clarify when you plan to remove browser.proton.enabled which allows to enable (more or less) old style of the browser?

The pref will likely be turned into a no-op during the Firefox 90 cycle.

Could you please consider keeping this option at least in the Firefox 91 ESR?

No, the overhead both in terms of code and in terms of complexity, is significant - so much so that I'm going to split this bug up into a few different dependencies, with a rough schedule as to when each of these is happening, with the goal of making uplifts in the 90 cycle straightforward (instead of having to rebase around conditionals that are there in one branch and not another).

If there are concrete issues you have with the new styling, please file bugs on those insofar as they are not on file already.

Points: 2 → ---
Component: Theme → General
Keywords: meta
OS: Unspecified → All
Hardware: Unspecified → Desktop
Summary: Remove non-Proton branches from our CSS and JS, and Proton prefs → [meta] Remove non-Proton branches from our CSS and JS, and Proton prefs

Plan document: https://docs.google.com/document/d/1M_OPsYyIzdyzcP2J7TJAsLMdAUlPS7h2J_AxSAxysqA/edit#

Salient details:

  1. From May 17, write and land patches in nightly 90 (no uplift) that remove relevant pref pushes/checks from all test code. This can be split up for the feature prefs and the main pref, and the main pref could be subdivided by directory if there are a lot of accesses, to make the individual patches small and straightforward to test and review.
  2. After May 20 (last non-RC beta), land patches that remove relevant pref checks from non-test code. This includes cleaning up CSS code, but not removing the stylo / CSS media queries.
  3. After that but before May 27 (soft freeze), land patches that remove cached versions of the prefs (gProton, PanelUI.protonAppMenuEnabled, CustomizableUI.protonToolbarEnabled, etc.), once they’re unused.
  4. After June 1, in the 91 cycle, remove the stylo/CSS code and the (now completely unused) preferences. Uplifting this to 90 isn’t needed (though could be done if relman wants it) as conflicts in those files should be trivial to resolve and uplift would be a no-op for 90, as all uses of the prefs will have been removed.

I'll file deps for these, and deps for those deps where appropriate.

Depends on: 1711467

The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Priority: P3 → --
Priority: -- → P3
Depends on: 1711506

(In reply to :Gijs (he/him) from comment #3)

Plan document: https://docs.google.com/document/d/1M_OPsYyIzdyzcP2J7TJAsLMdAUlPS7h2J_AxSAxysqA/edit#

So clearly, we did not reach the timeline in this doc. We'll aim to remove the remaining parts in the 91 cycle, to avoid keeping two implementations of everything around for ESR.

Restrict Comments: true

Hi, all -

While we're always glad for technical feedback in Bugzilla, we're confident in this decision, and intend to stick with it going forward. That said, we're making an effort to move design and high-level product feedback like this over to Ideas.mozilla.org; I hope you'll join and follow the related discussions over there.

You need to log in before you can comment on or make changes to this bug.