Closed Bug 1685490 Opened 3 years ago Closed 3 years ago

[Enhancement] Consider differently aligning the toggles in the Customization panel to their Section titles

Categories

(Firefox :: New Tab Page, enhancement, P1)

Desktop
All
enhancement

Tracking

()

VERIFIED FIXED
87 Branch
Tracking Status
firefox84 --- unaffected
firefox85 --- wontfix
firefox86 --- verified
firefox87 --- verified

People

(Reporter: mheres, Assigned: ewright)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image toggle alignement.png

[Affected versions]:

  • Firefox Beta 85.0b5 (Build ID: 20210105185604)

[Affected Platforms]:

  • Windows 10 x64

[Prerequisites]:

  • Have the latest Firefox Beta version installed and open.
  • Have browser.newtabpage.activity-stream.newNewtabExperience.enabled set to true.

[Steps to reproduce]:

  1. Open a new tab.
  2. Click the “Personalize” button.
  3. Observe the position of the toggles compared to the corresponding Section titles.

[Proposed result]:

  • The toggle is aligned differently, so it is lower compared to the current position.

[Current result]:

  • The toggle seems like it is slightly higher than the option it represents.

[Notes]:

  • When I tried lowering them with 5px they seemed more part of the section they represented in the menu, but that was only in English and did not take into account diacritics or any other aspect that the move might influence, design requirements, nor any standards.
  • Attached is a screenshot of the current behavior.

Can y'all prioritize this? Thx!

Flags: needinfo?(jgruen)
Flags: needinfo?(ewright)
Flags: needinfo?(ewright)
Priority: -- → P2
Assignee: nobody → ewright
Status: NEW → ASSIGNED
Priority: P2 → P1
Pushed by ewright@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cb5f069a6527
Align toggles and titles in customize menu r=prathiksha
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch

I am not able to verify that the change is observable comparing the first version without (Firefox Nightly 87.0a1 Build ID:20210126155519) and the latest available Nightly (Firefox Nightly 87.0a1 Build ID:20210127093943) on Windows 10.
Visually comparing them, the two look the same to me. I am also not able to verify that the change introduced a margin-top of 2 px for switches - using the Inspect tool didn't reveal it.
I am attaching screenshots of the visual comparison between Nightly versions, current behavior inspected and the result of using the Inspector tool.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Thank you, it looks like this did not bundle correctly.

Depends on: 1689198
Depends on: 1687970
No longer depends on: 1689198

(In reply to Maria Heres, :mheres, Ecosystem QA from comment #5)

I am not able to verify that the change is observable comparing the first version without (Firefox Nightly 87.0a1 Build ID:20210126155519) and the latest available Nightly (Firefox Nightly 87.0a1 Build ID:20210127093943) on Windows 10.
Visually comparing them, the two look the same to me. I am also not able to verify that the change introduced a margin-top of 2 px for switches - using the Inspect tool didn't reveal it.
I am attaching screenshots of the visual comparison between Nightly versions, current behavior inspected and the result of using the Inspector tool.

Thank you Maria, could you check this again, we've now landed the bundle correctly.

Depends on: 1689198

(In reply to Erica Wright [:ewright] from comment #7)

(In reply to Maria Heres, :mheres, Ecosystem QA from comment #5)

I am not able to verify that the change is observable comparing the first version without (Firefox Nightly 87.0a1 Build ID:20210126155519) and the latest available Nightly (Firefox Nightly 87.0a1 Build ID:20210127093943) on Windows 10.
Visually comparing them, the two look the same to me. I am also not able to verify that the change introduced a margin-top of 2 px for switches - using the Inspect tool didn't reveal it.
I am attaching screenshots of the visual comparison between Nightly versions, current behavior inspected and the result of using the Inspector tool.

Thank you Maria, could you check this again, we've now landed the bundle correctly.

The bug that fixes this was backeed out, I'll uupdate again once it lands

Bug 1687970 fixes the bundle issues. It was not backed out. I think this bug is ready for Maria to take another look.

Flags: needinfo?(jgruen)
Flags: needinfo?(mheres)

I have verified that a margin-top of 2px has been introduced for the toggles using Firefox Nightly 87.0a1 (Build ID: 20210128215644) on Windows 10, macOS 10.15.6, Linux Mint 20.

Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Flags: needinfo?(mheres)
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED

Comment on attachment 9199100 [details]
Bug 1685490 - Align toggles and titles in customize menu

Beta/Release Uplift Approval Request

  • User impact if declined: A small portion of users enrolled in our experiments won't be able to see these style changes to the newtab page
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): It's a one line stye change and it's behind a pref
  • String changes made/needed: None
Attachment #9199100 - Flags: approval-mozilla-beta?

Comment on attachment 9199100 [details]
Bug 1685490 - Align toggles and titles in customize menu

Approved for 86 beta 4, thanks.

Attachment #9199100 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

I have verified that a margin-top of 2px has been introduced for the toggles using Firefox Beta 86.0b4 (Build ID: 20210131185630) on Windows 10, Linux Mint 20 and macOS 11.1. The toggles are now better aligned with the text of the option they represent.

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

Attachment

General

Created:
Updated:
Size: