1249599 - [Linux] Broken Panel Menu after customizing the browser

Status: RESOLVED DUPLICATE of bug 1248582

(Firefox :: Toolbars and Customization, defect)

Description

[Vasilica Tamas, QA [:vtamas]]

[Affected versions]:
Firefox 47.0a1 (2016-02-18)

[Affected platforms]:
Ubuntu 12.04 64-bit

[Steps to reproduce]:
1.Launch Firefox with clean profile.
2.Click menu [≡] → select "Customize".
3.Drag a few items from toolbar and drop them into the panel menu.
4.Drag a few items from panel menu and drop them into the toolbar.
5.Exit from “Customize” mode.
6.Open the Panel Menu.

[Expected Results]:
The Panel Menu is correctly displayed.

[Actual Results]:
The Panel Menu is broken.
See screenshot:http://i.imgur.com/aX8a1TT.png

[Regression range]:
- I am unable to provide a regression window because of Bug 1230540
- Noticed that Firefox 37.0a1 from 2016-01-01 is not affected. 
- I will try to get a manually regression window as soon as possible.

Comment 1

[:Gijs (he/him)]

(In reply to Vasilica Mihasca, QA [:vasilica_mihasca] from comment #0)
> [Regression range]:
> - I am unable to provide a regression window because of Bug 1230540
> - Noticed that Firefox 37.0a1 from 2016-01-01 is not affected. 
> - I will try to get a manually regression window as soon as possible.

Ni for this. It might be easier to create a profile and set the pref for the speech synthesis to false in it manually, and then use that with mozregression's --profile switch.

Comment 2

[Vasilica Tamas, QA [:vtamas]]

(In reply to :Gijs Kruitbosch from comment #1)

> Ni for this. It might be easier to create a profile and set the pref for the
> speech synthesis to false in it manually, and then use that with
> mozregression's --profile switch.

Thanks Gijs! This really helped me.

Here is the regression window:

(m-i)
Last good revision: 600942ae9823ae85186cd613b65582078489daa4
First bad revision: 432ef38dab958e325c2e56dd4093be023c221043
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=600942ae9823ae85186cd613b65582078489daa4&tochange=432ef38dab958e325c2e56dd4093be023c221043

So, this issue seems to be regressed by Bug 1241832.

But, also noticed that this is a duplicate of Bug 1248582.