Closed
Bug 1279140
Opened 9 years ago
Closed 9 years ago
awesomebar displaying incorrect text UI for containers
Categories
(Firefox :: General, defect, P1)
Tracking
()
VERIFIED
FIXED
Firefox 50
People
(Reporter: kjozwiak, Assigned: baku)
References
(Blocks 1 open bug)
Details
(Whiteboard: [usercontextId], [domsecurity-active][uplift49+])
Attachments
(3 files)
222.36 KB,
image/png
|
Details | |
225.37 KB,
image/png
|
Details | |
929 bytes,
patch
|
Sylvestre
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
I ran into an issue where the container text UI under the awesome bar was incorrectly displaying the wrong description. Both the tab colour and the awesome bar image were correct, but the text portion of the UI was always displaying "Shopping" as it's text. I'll try reproducing and getting some STR, but in the meantime, I created this bug so we're aware that this is happening.
Examples:
* issue1.png - personal container (blue), using the correct image, however, the text UI is displaying "Shopping"
* issue2.png - work container (orange), using the correct image, however, the text UI is displaying "Shopping"
Build Used:
* fx50.0a1, buildID: 20160608030219, changeset: f8ad071a6e14
* https://archive.mozilla.org/pub/firefox/nightly/2016/06/2016-06-08-03-02-19-mozilla-central/
Reporter | ||
Comment 1•9 years ago
|
||
Updated•9 years ago
|
Priority: -- → P1
Comment 2•9 years ago
|
||
This is a big deal. Kamil, if you figure out STR, please provide them. Thank you!
Reporter | ||
Comment 3•9 years ago
|
||
Managed to figure it out :)
STR:
* install/launch a fresh copy of the latest m-c
* open about:config -> privacy.userContext.enabled;true
* restart m-c
* open a new container tab via file -> new container tab -> personal
* switch to the personal container tab
* select hamburger menu -> customize
* place the "open container tab" icon on the toolbar and select "exit customization"
* click on the "open container tab" icon that you've placed on the toolbar and select a work container
You'll notice that the container text under the awesomebar will appear is "Personal" rather than "Work". I've attached a video to illustrate the issue:
* https://youtu.be/wwFdu1EAeM4
Assignee | ||
Comment 4•9 years ago
|
||
ULElement.value doesn't exist. This patch uses setAttribute().
Attachment #8761483 -
Flags: review?(gijskruitbosch+bugs)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → amarchesini
Updated•9 years ago
|
Whiteboard: [userContextId] → [usercontextId], [domsecurity-active]
Comment 5•9 years ago
|
||
(In reply to Andrea Marchesini (:baku) from comment #4)
> Created attachment 8761483 [details] [diff] [review]
> label.patch
>
> XULElement.value doesn't exist.
No, but the label XBL binding has a value property: http://searchfox.org/mozilla-central/source/toolkit/content/widgets/text.xml#19-20
In other words, the existing code "should work".
> This patch uses setAttribute().
Why isn't the binding present yet in this case?
Flags: needinfo?(amarchesini)
Comment 6•9 years ago
|
||
Comment on attachment 8761483 [details] [diff] [review]
label.patch
Review of attachment 8761483 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/base/content/browser.js
@@ +4126,5 @@
>
> let indicator = document.getElementById("userContext-indicator");
> indicator.style.listStyleImage = "url(" + identity.icon + ")";
>
> hbox.hidden = false;
I suspect moving this before the label.value assignment would fix this in a more readable way.
Attachment #8761483 -
Flags: review?(gijskruitbosch+bugs)
Assignee | ||
Comment 7•9 years ago
|
||
> I suspect moving this before the label.value assignment would fix this in a
> more readable way.
It doesn't. I suspect the bug is somewhere else. but using setAttribute directly it works.
Flags: needinfo?(amarchesini) → needinfo?(gijskruitbosch+bugs)
Pushed by amarchesini@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b0d48deeae7b
The label of the container in awesomebar should follow the container type, r=Gijs
Assignee | ||
Comment 9•9 years ago
|
||
We discussed on IRC and I'll file a followup to debug more why label.value doesn't work as it should.
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(gijskruitbosch+bugs)
Comment 10•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
Comment 11•9 years ago
|
||
Please file bugs in the product / component where the relevant code lives.
Component: DOM: Security → General
Product: Core → Firefox
Target Milestone: mozilla50 → Firefox 50
Is this important enough to uplift for test pilot? Im going to er on the side of yes, unless someone else disagrees.
Whiteboard: [usercontextId], [domsecurity-active] → [usercontextId], [domsecurity-active][uplift49+]
Comment on attachment 8761483 [details] [diff] [review]
label.patch
Approval Request Comment
[Feature/regressing bug #]: Testpilot for containers
[User impact if declined]: UI broken for testpilot users.
[Describe test coverage new/current, TreeHerder]: Testing done manually, can be easily reproduced and observed.
[Risks and why]: One line fix to correct text. In order to do a Test Pilot experiment for Containers in September / Firefox 49 release, we need this code in release. Without it, testing is delayed until November and getting the capabilities of the feature to users is delayed even further.
[String/UUID change made/needed]:None
Attachment #8761483 -
Flags: approval-mozilla-aurora?
Reporter | ||
Comment 14•9 years ago
|
||
Using the latest version of nightly [1], I went through verification using the STR from comment #0 without any issues. I also went through several other combinations:
* disabled/enabled containers and ensured this issue wasn't occurring once the "Open Container Tab" icon disappeared/reappeared
* rather than using the toolbar, opened several container tabs via the Hamburger Menu
* rather than opening the initial container via file -> new container tab -> personal, used the following:
** closed all FX windows and opened containers via file -> new container tab -> personal
** opened several containers via the context menu
I also ensured that the correct context is being used via the cookie manager under about:preferences#privacy
[1] https://archive.mozilla.org/pub/firefox/nightly/2016/07/2016-07-12-03-02-34-mozilla-central/
(In reply to Paul Theriault [:pauljt] from comment #13)
> Comment on attachment 8761483 [details] [diff] [review]
> label.patch
>
> Approval Request Comment
> [Feature/regressing bug #]: Testpilot for containers
> [User impact if declined]: UI broken for testpilot users.
> [Describe test coverage new/current, TreeHerder]: Testing done manually, can
> be easily reproduced and observed.
> [Risks and why]: One line fix to correct text. In order to do a Test Pilot
> experiment for Containers in September / Firefox 49 release, we need this
> code in release. Without it, testing is delayed until November and getting
> the capabilities of the feature to users is delayed even further.
> [String/UUID change made/needed]:None
Commenting further to clarify the risk of this change as requested via email. This is a simple one line change to correct a text value. This will not affect regular users, only users who have enabled containers manually via a preference or the Test Pilot users.
Updated•9 years ago
|
status-firefox49:
--- → affected
Comment 16•9 years ago
|
||
Comment on attachment 8761483 [details] [diff] [review]
label.patch
Needed for the Test Pilot container/identity feature, taking it.
Attachment #8761483 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Updated•9 years ago
|
Flags: qe-verify+
Comment 17•9 years ago
|
||
bugherder uplift |
Reporter | ||
Comment 18•9 years ago
|
||
Went through verification using the following buid:
* https://archive.mozilla.org/pub/firefox/nightly/2016/07/2016-07-28-00-40-10-mozilla-aurora/
** fx49.0a2 buildId: 20160728004010, changeset: 5d074cab0660
Test Cases:
* went through the original STR from comment#3 without any issues
* went through the test cases from comment#14 without any issues
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•