[Proton] Translation notification bar is broken
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect)
Tracking
(firefox-esr78 unaffected, firefox87 unaffected, firefox88 unaffected, firefox89 verified, firefox90 verified)
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox87 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | verified |
firefox90 | --- | verified |
People
(Reporter: nayinain, Unassigned)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [proton-infobars])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
- Set
browser.proton.infobars.enabled
,browser.translation.detectLanguage
and browser.translation.ui.showto
truein
about:config`. - Restart Nightly.
- Open https://www.baidu.com/
Actual results:
The translation notification bar is broken.
Regression window:
2021-03-29T22:37:08.294000: INFO : application_version: 89.0a1
2021-03-29T22:37:08.297000: INFO : platform_buildid: 20210329023619
2021-03-29T22:37:08.297000: INFO : platform_changeset: 12ad213232f380306f4d245504c0c7211a44f091
2021-03-29T22:37:08.297000: INFO : platform_repository: https://hg.mozilla.org/integration/autoland
2021-03-29T22:37:08.297000: INFO : platform_version: 89.0a1
2021-03-29T22:37:17.898000: INFO : Narrowed integration regression window from [5682b038, 512780b9] (3 builds) to [12ad2132, 512780b9] (2 builds) (~1 steps left)
2021-03-29T22:37:17.911000: DEBUG : Starting merge handling...
2021-03-29T22:37:17.911000: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=512780b9dd3ccbd9457fdcc9ccfbc412c9d87fef&full=1
2021-03-29T22:37:17.912000: DEBUG : redo: attempt 1/3
2021-03-29T22:37:17.912000: DEBUG : redo: retry: calling _default_get with args: ('https://hg.mozilla.org/integration/autoland/json-pushes?changeset=512780b9dd3ccbd9457fdcc9ccfbc412c9d87fef&full=1',), kwargs: {}, attempt #1
2021-03-29T22:37:17.916000: DEBUG : urllib3.connectionpool: Resetting dropped connection: hg.mozilla.org
2021-03-29T22:37:19.338000: DEBUG : urllib3.connectionpool: https://hg.mozilla.org:443 "GET /integration/autoland/json-pushes?changeset=512780b9dd3ccbd9457fdcc9ccfbc412c9d87fef&full=1 HTTP/1.1" 200 None
2021-03-29T22:37:19.390000: DEBUG : Found commit message:
Bug 1690333 - Proton infobar styles r=jawsDifferential Revision: https://phabricator.services.mozilla.com/D104585
2021-03-29T22:37:19.391000: DEBUG : Did not find a branch, checking all integration branches
2021-03-29T22:37:19.396000: INFO : The bisection is done.
2021-03-29T22:37:19.400000: INFO : Stopped
Comment 2•4 years ago
|
||
Set release status flags based on info from the regressing bug 1690333
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Please note that the Bergamot extension [1] requires browser.proton.enabled set to be true so ideally this should be fixed before the infobars graduate to the main Proton preference (bug 1702330).
[1] https://github.com/mozilla-extensions/bergamot-browser-extension
Comment 4•4 years ago
|
||
There's a fix for this in bug 1702327 (it just leaves this infobar with the old styling since it's very custom compared to the other infobars).
Updated•4 years ago
|
Comment 5•4 years ago
|
||
This should now be fixed by bug 1702327
Updated•4 years ago
|
Comment 6•3 years ago
|
||
Verified using the latest Firefox 89 beta 2 and the latest Nightly 90.0a1 - the translation infobar is displayed with the old style. Verified on macOS BigSur 11.2, Windows 10 x64, and Ubuntu 20.04 x64.
However, during verification, I noticed some situations in which the Translation infobar can change position and is affecting the stacking and Proton design (please see the screenshot). Mark, is this behavior expected?
Updated•3 years ago
|
Comment 7•3 years ago
|
||
What do you mean by "change position"? I see the translation bar is first in the first screenshot, then second. Are you saying that it initially appeared at the top then moved on its own to the bottom? I'd expect it to be the lowest infobar when it appears, and opening a new (tab-specific) infobar would appear under it. If you had the first screenshot, then close and retriggered the translation infobar I would expect it to move like that
Comment 8•3 years ago
|
||
(In reply to Mark Striemer [:mstriemer] from comment #7)
What do you mean by "change position"? I see the translation bar is first in the first screenshot, then second. Are you saying that it initially appeared at the top then moved on its own to the bottom? I'd expect it to be the lowest infobar when it appears, and opening a new (tab-specific) infobar would appear under it. If you had the first screenshot, then close and retriggered the translation infobar I would expect it to move like that
Ok, so basically I'm seeing the intended behavior. And no, it doesn't move by itself. If I open the translation infobar first and then another tab specific, this will be placed under the translation, and vice-versa (the translation one is placed under another tab specific infobar if it's triggered secondly).
What I wasn't expecting was to see the translation infobar between the 2 other proton-styled info bars. I would have expected for it to be somehow separated by the proton-styled ones (maybe always on the bottom, since the browser-specific ones are always on top). At the time being, especially when the translation infobar is in the middle everything seems out of place as the buttons and the text is bigger and differently styled. Do you know if the translation infobar will be reworked in the near future?
Comment 9•3 years ago
|
||
We have bug 1703322 on file to update the translation bar to proton styling. I haven't heard anything about prioritising that right now and I suspect it would be out of scope for proton
Comment 10•3 years ago
|
||
(In reply to Mark Striemer [:mstriemer] from comment #9)
We have bug 1703322 on file to update the translation bar to proton styling. I haven't heard anything about prioritising that right now and I suspect it would be out of scope for proton
Great, thanks, Mark!
Based on Comment 6 and Comment 7, setting the status of this to Verified fixed.
Updated•1 year ago
|
Description
•