[Ubuntu] Going through the signup process with a new sync'd account causes the URL text to appear faded out on RTL builds
Categories
(Firefox :: Address Bar, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | affected |
firefox67 | --- | wontfix |
firefox68 | --- | wontfix |
firefox69 | --- | wontfix |
firefox70 | --- | wontfix |
firefox71 | --- | unaffected |
People
(Reporter: cfogel, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
29.99 KB,
image/png
|
Details |
Affected versions
- 70.0b13;
Affected platforms
- Ubuntu 16.04, Ubuntu 18.04
Steps to reproduce
Setup:
Install the 70.0b13 RTL-arabic build;
STR:
(in TAB 1)
- Launch Firefox with new profile;
- Click avatar icon;
- Click Turn on Sync... ;
- Enter email, click next (any mail, even disposable/invalid);
Enter valid password, enter age > 21, click next
Click create account and save the login - Click on the other tab(TAB 2);
- Input any address (about:logins)
Expected result
- link is properly displayed;
Actual result
- right side of the text appears faded out;
Regression range
- will provide one asap;
Additional notes
- attached screenshot with the issue;
- issue appears to be limited to the first 2 tabs;
- in some cases swapping between or opening a new 3rd tab clears the issue;
- restarting the browser fixes the issue as well;
- nightly builds 71.0a1(09/10/2019) appear not to have this issue;
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Was this not reproducible on Windows/Mac ?
If this doesn't reproduce in nightly I suspect it was fixed in bug 1496158, but the steps in comment #0 should never have been broken - have you confirmed 69 was/wasn't affected?
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
Had some time to double check.
Indeed Windows(10) and MacOS(10.13.6) turn out to be affected as well.
:snegritas confirmed yesterday that 69.0.3 was affected and HE localised builds as well so it's not limited to only the Arabic ones.
Comment 3•5 years ago
|
||
I have tried to find a regression for this bug and I checked the versions afected up to versions 67 and 68, it appears that the about:logins
page has been introduced with this issue for the RTL builds, so i will clear the regression keywords.
Comment 4•5 years ago
|
||
(In reply to Negritas Sergiu from comment #3)
I have tried to find a regression for this bug and I checked the versions afected up to versions 67 and 68, it appears that the
about:logins
page has been introduced with this issue for the RTL builds, so i will clear the regression keywords.
Does it not reproduce with other about: URLs, like about:config or about:support ? Comment #0 says "any address"...
Comment 5•5 years ago
|
||
Upon further investigation I've noticed that indeed it's not limited to that page. Adding the keywords back and will look into this issue further next week.
So far what we got is that is reproducing till the version of 66.0.1 and on the beta versions till 65.0b3.
Comment 6•5 years ago
|
||
If this doesn't reproduce on 71, is this worth investigating further if ESR68 is the only affected product which could plausibly still be fixed here? I'm leaning wontfix personally.
Comment 7•5 years ago
|
||
So... this was fixed by bug 1496158, yes? If we want to uplift bug 1496158 to ESR 68, we can take that discussion to that bug, but as for this bug, it's fixed or worksforme, right?
Comment 8•5 years ago
|
||
(In reply to Drew Willcoxon :adw from comment #7)
So... this was fixed by bug 1496158, yes? If we want to uplift bug 1496158 to ESR 68, we can take that discussion to that bug, but as for this bug, it's fixed or worksforme, right?
I think what's confusing me is how this is even happening without 1496158. I guess we can shrug and move on given that the steps as filed are fixed, but it's surprising that this behaviour is there in RTL and it might indicate other, similar issues that were not fixed by 1496158.
Marco, what do you think?
Comment 9•5 years ago
|
||
Based on comment 7 I looked to find if this issue was reproducible with a nightly version build earlier from when the fix was made for the bug 1496158 and I was not able to reproduce the issue. I also managed to find a regression between Fx 61.0b14 which is the last good and the Fx 62.0b3 which is the first bad. Here you have a pushlog https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=585281dde9604ddd197693ca5330f2b95987a181&tochange=1716b76aa7b8df189e74bf87394d3a11e0c5ac12.
Comment 10•5 years ago
•
|
||
(In reply to :Gijs (he/him) from comment #8)
I think what's confusing me is how this is even happening without 1496158.
Afaict it was already happening before Bug 1496158, likely some race condition with the way we set the textoverflow attribute (reflow, raf, ...).
The addition of the rtldomain is wallpapering the problem, though I don't understand this:
(In reply to Negritas Sergiu from comment #9)
Based on comment 7 I looked to find if this issue was reproducible with a nightly version build earlier from when the fix was made for the bug 1496158 and I was not able to reproduce the issue.
Did it broke at 62 and then something else fixed it later? Or did you just test ONE nightly before bug 1496158? There were other fixes related to this part...
Comment 11•5 years ago
|
||
(In reply to Marco Bonardo [::mak] from comment #10)
(In reply to :Gijs (he/him) from comment #8)
I think what's confusing me is how this is even happening without 1496158.
Afaict it was already happening before Bug 1496158, likely some race condition with the way we set the textoverflow attribute (reflow, raf, ...).
The addition of the rtldomain is wallpapering the problem, though I don't understand this:(In reply to Negritas Sergiu from comment #9)
Based on comment 7 I looked to find if this issue was reproducible with a nightly version build earlier from when the fix was made for the bug 1496158 and I was not able to reproduce the issue.
Did it broke at 62 and then something else fixed it later? Or did you just test ONE nightly before bug 1496158? There were other fixes related to this part...
I tried with a few nightly versions before the fix but I didn't manage to reproduce the issue because when you try to register for a new sync account it automatically opens a new tab and from the additional notes from comment 0 the issue is not reproducible after opening a new tab. On beta versions you can register a new account from the same tab.
Comment 12•5 years ago
|
||
Considering the impact and the fact it's not easily reproducible, plus the wallpapering fix, I'll set this to a P5. If someone has time and will to investigate the race condition, a patch will be welcome, but it doesn't look like something the team can spend time on, for now.
Updated•4 years ago
|
Description
•