The CFR Pin tabs doorhanger is not triggered on Ubuntu
Categories
(Firefox :: Messaging System, defect, P5)
Tracking
()
People
(Reporter: asoncutean, Assigned: andreio)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Affected versions
- 80.0b3
Affected platforms
- Ubuntu 16.04 (x64 and x86)
Steps to reproduce
- Open a new tab and navigate to any of the targeted web app that supports CFR Pin tabs (eg. facebook.com or twitter.com)
- Change the system's time to 17 min into the future
- Repeat the first two steps again
- Open a new tab and navigate to the designated web app again
Actual result
- The "CFR Recommendation" button is not displayed
Expected result
- The "CFR Recommendation" button is displayed in the right part of the "Address Bar"
Regression range
- I will investigate a little bit around this issue as soon as possible.
Additional notes
- Not reproducible in Nightly
Comment 1•4 years ago
|
||
:Anca, is this specific to pin-tabs only, or are CFRs broken entirely on Ubuntu?
Reporter | ||
Comment 2•4 years ago
|
||
(In reply to Dan Mosedale (:dmose, :dmosedale) from comment #1)
:Anca, is this specific to pin-tabs only, or are CFRs broken entirely on Ubuntu?
-
We‘ve encountered NO problem with the "Take this recipe to the kitchen" and
"Read this on the go" CFR doorhangers on long content form targeted sites or recipes / cooking ones. -
The other issue was with the URLs ending in .pdf (bug 1656859, that you are already aware).
Reporter | ||
Comment 3•4 years ago
|
||
At the time this issue was submitted, we were a little bit under the clock with the testing schedule, so apparently I've used an older Nightly in the hurry. I now confirm the issue on latest Nightly 81.0a1 (2020-08-07) , not only on Ubuntu 16.04, also on Ubuntu 18.04.
I've tried to determine a regression range manually to make sure that the frequently time changing is not messed up without a restart and the results to be conclusive. I restrained it to the following: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=db2e1d780268ab0a7dca1ea1ca81febcb33e926e&tochange=0f9c5a59e45d34f53ab4d44058ed016d4bacf942. The only CFR bug in the list is 1631456, so I am pointing it out as a potential regressor, but not sure if it is indeed the real "culprit" here.
Comment 4•4 years ago
|
||
andrei could you look at this and see if the proposed regressing bug is correct?
Assignee | ||
Comment 5•4 years ago
|
||
I was able to trigger the CFR and telemetry doesn't show any issues (nightly channel or otherwise).
I will try to see if this is somehow platform specific.
Assignee | ||
Comment 6•4 years ago
|
||
Verified on Ubuntu 18.04 x64 with Beta 80.0 and Firefox 79.0 with the help of :mcoman.
Updated•4 years ago
|
Description
•