Created attachment 422266 [details] screenshot of right-click menu In >=www-client/firefox-43.0 the right click context menu shows all options, rather than the contextual options for what is being clicked on (see attached screenshot). This affects both www-client/firefox-43.0 and www-client/firefox-44.0_beta4
This also happens with a completely clean profile www-client/firefox-44.0_beta4::mozilla was built with the following: USE="dbus ffmpeg gmp-autoupdate gstreamer hwaccel jemalloc3 jit minimal startup-notification -bindist -custom-cflags -custom-optimization -debug -egl -gstreamer-0 -gtk3 -hardened (-neon) (-pgo) -pulseaudio (-qt5) (-selinux) -system-cairo -system-icu -system-jpeg -system-libevent -system-libvpx -system-sqlite -test -wifi" ABI_X86="64" CFLAGS="-march=native -pipe" CXXFLAGS="-march=native -pipe" LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-rpath=/usr/lib64/firefox"
Someone on the forum claimed, that setting system-icu fixes that, yet a folowup from a different user suggests that it might be even more quirky.
This happens on a clean profile and in safe mode, even when switching users it is bugged. Firefox-bin is fine though, so it must be something in the build. www-client/firefox-43.0::gentoo was built with the following: USE="dbus gmp-autoupdate gstreamer hwaccel jemalloc3 jit minimal pulseaudio -bindist -custom-cflags -custom-optimization -debug -egl -gstreamer-0 -gtk3 -hardened (-neon) (-pgo) (-selinux) -startup-notification -system-cairo -system-icu -system-jpeg -system-libvpx -system-sqlite -test -wifi" ABI_X86="64" LINGUAS="-af -ar -as -ast -be -bg -bn_BD -bn_IN -br -bs -ca -cs -cy -da -de -el -en_GB -en_ZA -eo -es_AR -es_CL -es_ES -es_MX -et -eu -fa -fi -fr -fy_NL -ga_IE -gd -gl -gu_IN -he -hi_IN -hr -hu -hy_AM -id -is -it -ja -kk -km -kn -ko -lt -lv -mai -mk -ml -mr -nb_NO -nl -nn_NO -or -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si -sk -sl -son -sq -sr -sv_SE -ta -te -th -tr -uk -vi -xh -zh_CN -zh_TW" CFLAGS="-march=native -pipe" CXXFLAGS="-march=native -pipe" LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-rpath=/usr/lib64/firefox"
I can confirm the fact that the issue goes away on building with system-icu use flag enabled.
(In reply to Amit Prakash Ambasta from comment #4) > I can confirm the fact that the issue goes away on building with system-icu > use flag enabled. Yes, confirmed.
Upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=1238143 -- thanks for filing, Markus.
How many of you are using an ivybridge cpu and march=native? I see everyone saying they can duplicate it by I have no emerge --info from anyone. Please add your emerge --info do not just say happens to me it is rather useless to debug with such comments.
Created attachment 422532 [details] emerge --info -march=amdfam10 here. Confirmed that system-icu helps. For me the issue happened after upgrading from gcc 4.9.3 to 5.3.0. I rebuilt large parts of my system in the process, due to the abi change. But I only switched from FF 32.0-r2 to 43.0 shortly before, and am not sure that I ever had a 43.0 up and running before the gcc switch, so this might be completely unrelated if it's only happening to me.
Upstream claims to have solved: https://bugzilla.mozilla.org/show_bug.cgi?id=1238143#c2 So, I tried and finally got compiled this upstream version using these flags: www-client/firefox-43.0.4::pmaci USE="-bindist -custom-cflags -custom-optimization dbus -debug egl -gmp-autoupdate gstreamer -gstreamer-0 -gtk3 -hardened hwaccel jemalloc3 -jit minimal (-neon) (-pgo) pulseaudio (-selinux) -startup-notification -system-cairo system-icu system-jpeg system-libvpx -system-sqlite {-test} -wifi" Many tries with failed builds, I saw jpeg and egl errors until I got this mix of USE flags working.
This is odd, I just verified version of bundled and system-icu, they are the same version. I might have a clue tho so give me time to track down and provide you a patch to test with.
Created attachment 422534 [details, diff] Always build with intl-api being exposed Please test apply patched. Do not forget to use -system-icu
Has been confirmed fixed, if problem should arise after re-emerging later please feel free to reopen bug report.
Yes, --with-intl-api also fixes the problem. Thanks for looking into it!
*** Bug 572200 has been marked as a duplicate of this bug. ***
