1762292 - Restore Zap capability potentially with double lines for hero text

Status: VERIFIED FIXED

(Firefox :: Messaging System, enhancement, P1)

Description

[Ed Lee :Mardak]

Attachment: single zap example

Designs currently have a double zap under "Yous" of 100 Thank Yous. But that might have spacing/overlap issues for translations that have "Yous" not as the last word. It seems like current styling should work okay with a single zap.

Comment 1

[Ed Lee :Mardak]

emcminn, with bug 1762488 patch adding zap for any Localized, this bug should just be activating zap, e.g., hero_text: { zap: true, …

Comment 2

[Emily McMinn :emcminn]

Attachment: Bug 1762292 - Turn on Zap for hero text r=mviar

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6dd62bffb5c1
Turn on Zap for hero text r=Mardak,mviar

Comment 4

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/6dd62bffb5c1

Comment 5

[Alex Finder]

== Change summary for alert #33748 (as of Wed, 06 Apr 2022 04:42:32 GMT) ==

Improvements:

Ratio	Test	Platform	Options	Absolute values (old vs new)
9%	welcome ContentfulSpeedIndex	macosx1015-64-shippable-qr	cold fission webrender	1,942.00 -> 1,775.92
7%	welcome ContentfulSpeedIndex	macosx1015-64-shippable-qr	fission warm webrender	1,822.58 -> 1,686.33

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=33748

Comment 6

[Alex Finder]

Hello Emily! Could you help figure out which of the two patches (this one or 1762290) corresponds to the performance improvement for the alert posted above ? Thank you!

Comment 7

[Emily McMinn :emcminn]

Hi Alex!
I've chatted with my team a bit and the only thing we can come up with is that the perf improvement may be coming from https://phabricator.services.mozilla.com/D142709; which changed the about:welcome background image to a 3kb .svg (the previous image was a 103kb .avif). These patches were all stacked and landed together, which could explain why the alert is showing up here instead. (Oddly D1422709 has a regression attached to it.) I'll make a note here if I come across anything new.

Comment 8

[Simona Rosu [:srosu], Ecosystem QA]

This enhancement was part of the work done on QA-1448 for which we sent a Preliminary checkpoint. Considering this I am marking it as Verified.

Comment 9

[Alex Finder]

Hi Emily! Thank you for the response! Unfortunately, there was a regression associated with this revision, so I added both 1762292 and 1762290 as regressed by the logged regression defect. Once the source of the regression is identified between the two bugs, could you please remove 1765183 from the other bug's "Regressed by" field ? Thanks!