search

netrunner-rolling / 2018.08

0 stars 0 forks source link

firefox: misses top menu and bookmark bar #15

Open star-buck opened 6 years ago

star-buck commented 6 years ago

Before updating anything that might break and reset already installed systems, lets think how we can potentially fix that.

@NuLogicSystems : I do not want to see the package updated accidently before we have this figured 101% out.

If tests show this would not be possible, we ship it in next ISO only and leave it like that for now.

NuLogicSystems commented 6 years ago

Could you give me an example? I'm not seeing this on any of my systems, both are still there when I launch Firefox. I haven't updated the netrunner-settings-firefox package since prior to building the 2018.06-rc5 ISO. Is that the package you are referring too?

This might be an issue already fixed in a cck2 update, I'll look into this on Monday. https://github.com/mkaply/cck2wizard/releases

We do need to also keep in mind that the distribution directory, AutoConfig and CCK2 will no longer work with firefox 62. I'm investigating a transition of our customization's into Firefox's new enterprise policy support mechanism. However, I could use some help on this front.

https://mike.kaply.com/2018/04/24/enterprise-policy-support-in-firefox/ https://mike.kaply.com/2018/05/09/an-enterprising-future/

NuLogicSystems commented 6 years ago

I had another thought this morning. The firefox-kde-opensuse package is not only compiled with the plasma patches, but also with the Gentoo global menu, etc. patches. As such, If there is a global menu widget in use on the system, these could have been moved there. But for what it's worth, I still can not reproduce this issue.

NuLogicSystems commented 6 years ago

While testing package updates on my own systems, I still can not reproduce this issue as described. Nothing that I package effects settings in the end users home directory.

There is also effectively no way of shipping application and/or settings packages only on the ISO without breaking support for existing systems, these packages would need to be updated in the repositories for them to be installed. The only other method would be to put the settings directly in the ISO overlay's, and not package them. The problem there, is that issues like the one I just mentioned above regarding Firefox 62+ sand boxing AutoConfig, etc.., that will cause our current settings to stop working, would leave us with no way of fixing these kinds of issues for existing users from on our end.

Note: Since shadeslayer is the one that initially changed our settings packages to use CCK2, we really could use his input on how to move forward with these now that CCK2, and the older methods, will no longer work in Firefox 62+.

NuLogicSystems commented 6 years ago

I can confirm that Firefox 62 has a sandboxed autoconfig and no longer loads cck2, etc. I'm going over these to figure out the new policy mechenism, and how to implement our changes again using them: https://github.com/mozilla/policy-templates

star-buck commented 6 years ago

Can you please add a ticket under general netrunner, so also netrunner debian orofits and we solve it together?