Infrastructure

It has been discovered that we need to clear our browser's cached data for LibO Gerrit. Web editing also did not work due to this cache issue. I think you are facing the same problem and because your Chrome probably did not have cache history for Gerrit, it worked.

The Document Foundation Redmine schrieb am 15-Nov-20 um 09:05:

Seamonkey has no option to remove single entries from the cache, but can
only empty the total cache. But calling the site with an empty cache
does not solve the problem, I still have no buttons.

Could it be related to SeaMonkey not supporting some newer web technologies? Looking at their release notes, it is not at all clear to me what is the core Firefox version they are tracking. They speak about picking security fixes from both Firefox 60 and 78, which sounds kind of confusing.

Guilhem Moulin wrote:

Beluga Beluga wrote:

Could it be related to SeaMonkey not supporting some newer web technologies?

Ah yeah, good point. Regina Henschel , you can also try our stage instance at https://gerrit-stage.documentfoundation.org/ .

That results in "502 Bad Gateway".

The gerrit 3.1 → 3.2 upgrade includes a Polymer upgrade from 2.x to 3.x. AFAICT SeaMonkey 2.49.3 is based on Firefox 52 ESR but the Polymer 3.0 compatibility matrix doesn't mention Firefox <59: https://polymer-library.polymer-project.org/3.0/docs/browsers .

Regina Henschel wrote:

Ah yeah, good point. Regina Henschel , you can also try our stage instance at https://gerrit-stage.documentfoundation.org/ .

That results in "502 Bad Gateway".

Intentionally brought the stage instance back to sleep on Nov 24, 4 days after the message, this instance is in no way meant to be running at all time. Please try again — will stop it again in 24h.

Guilhem Moulin wrote:

Regina Henschel wrote:

Ah yeah, good point. Regina Henschel , you can also try our stage instance at https://gerrit-stage.documentfoundation.org/ .

That results in "502 Bad Gateway".

Intentionally brought the stage instance back to sleep on Nov 24, 4 days after the message, this instance is in no way meant to be running at all time. Please try again — will stop it again in 24h.

That too has no buttons. And on both (gerrit.libreoffice.org or gerrit-stage.documentfoundation.org), I cannot comment patches from others.

Regina Henschel wrote:

That too has no buttons. And on both (gerrit.libreoffice.org or gerrit-stage.documentfoundation.org), I cannot comment patches from others.

Thanks for trying. I guess that confirms FF <52ESR (released 2017-03-07) and derivatives are unfortunately not supported.

According to https://en.wikipedia.org/wiki/SeaMonkey#Release_history the latest stable release of SeaMonkey, 2.53.5.1, is based on Firefox 60.8. Thus, it should work with Gerrit's UI based on the Polymer support table Guilhem linked to.

Regina: can you try with the latest SeaMonkey?

I have now Seamonkey 2.53.5.1. I still have no buttons. For https://gerrit.libreoffice.org/c/core/+/107792 for example, I should have "Revert" and I should have vertical dots with "Download" and "Cherry Pick". But there is nothing.

In the recent Gerrit versions, Polymer stuff was rewritten to use Lit. I tested our Gerrit with SeaMonkey 2.53.12 as well as 2.53.13 Beta 1 and the layout has severe problems. However, this is not something we can tackle with our current resources. Possibly after we hire a web developer we can consider contributing something that helps.

That said, in my opinion the pressure is on SeaMonkey devs to upgrade the Firefox rendering engine. Apparently they are using some old version even though they cherry-pick various fixes to other parts from more recent Firefox versions.