Skip to content

Conversation

@Eijebong
Copy link
Contributor

One thing that bothered me recently while editing rules is that the form is very unhelpful wrt what got modified already. There's no way to know if you misclicked on a x and no way to see the final state of the rule before you save it. This adds a button at the bottom showing you the number of changes and when clicked, pops a RuleCard comparing the current state of the rule with the one pre-edition.

Worth noting that when editing a rule with scheduled changes, it will compare it against the currently used one instead of the one containing the scheduled changes.

The one thing that is a bit unfortunate is that I had to rewrite how the fabs work on this page to avoid having a third CSS rule to align a button... That's because the SpeedDial really wants its place in the bottom right and if we don't force the fab container 10rem to the right when it's present then it will be displayed below the speed dial.

Screenshots (taken on a tiny window to save space here...)

No changes to the rule:

image

With some changes:

image

When clicking on the "preview changes" button:

image

One thing that bothered me recently while editing rules is that the form
is very unhelpful wrt what got modified already. There's no way to know
if you misclicked on a `x` and no way to see the final state of the rule
before you save it. This adds a button at the bottom showing you the
number of changes and when clicked, pops a RuleCard comparing the
current state of the rule with the one pre-edition.

Worth noting that when editing a rule with scheduled changes, it will
compare it against the currently used one instead of the one containing
the scheduled changes.

The one thing that is a bit unfortunate is that I had to rewrite how the
fabs work on this page to avoid having a third CSS rule to align a
button... That's because the SpeedDial really wants its place in the
bottom right and if we don't  force the fab container 10rem to the right
when it's present then it will be displayed below the speed dial.
@Eijebong Eijebong requested a review from a team as a code owner December 19, 2025 12:08
Copy link
Contributor

@ahal ahal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you're looking for more than just a rubberstamp, you might want to block on someone else's review.. but looks reasonable at least.

@Eijebong Eijebong merged commit b2e29ec into mozilla-releng:main Jan 5, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants