[STR]:
1.Open new/uncached session
2.Navigate to https://voice.allizom.org/en/speak (without being logged in)
3.Record a clip then click "back arrow button" located in the upper left corner
4.Click "Submit clips" from "Finish recording first" prompt
5.Click "I agree" button

[Expected result]:
The clip should be uploaded and the "Finish recording first" prompt should be automatically close

Describe the bug

The "next" parameter is wrong when resolving comment, leading to wrong unit after that.

To Reproduce

Steps to reproduce the behavior:

1. Go to unit with (unresolved) comment using an absolute URL (https://hosted.weblate.org/translate/weblate/application/en/?checksum=d815ce5ce5b24771#comments)
2. Click on resolve
3. You are redirected to a different unit

**

Subject of the issue

Right now its not possible to share individual announcements. If we can provide a link with unique time stamp, the URL can be shared.

Expected behaviour

The time stamp should be a unique URL

Barcode image should be displayed on the product page, not only barcode numbers.

Rationale:

• it becomes easier to test our mobile apps with products we don't have physically
• it becomes easier to compare Open Food Facts data with other mobile apps
• it makes data more trustable: I can verify the barcode of my product is the same as displayed on the web page
• some people, for whatever

In #147 we modified the reply sending logic so that it first sets hyperlinks to a temp value and rely on promises to fill in hyperlinks after loading finishes.

However, the procedure may fail and cause forever polling scenario like this:
https://cofacts.g0v.tw/reply/H4TBinABWiTSPYAZPHxn

Needs further discussion on

• How many replies are affected
• How this can be mitigated

Estamos usando a versão 6.6.5 da biblioteca, mas ela tem uma comunidade super ativa e já está na versão 7.19!
Essa tarefa é pra simplesmente mudar pra usar a versão mais recente, verificando se não quebrou o layout. Opcionalmente podemos estudar as novas features que foram implementadas nesse meio tempo pra ver se alguma é interessante pra nós :)

Github da Sweetalert2:
https://github.com/swee

As-is

1. After inputting reason, the reason submission button jumps up and cancels the first click
2. During submission, there is no visual feedback indicating that the reply request is being sent

To-be

1. Don't change reason input height when reason input is

Until now, amti's testing has been entirely manual. There have been three reasons for this
decision:

1. amti began as a tool I built for myself. Originally, I wanted to demo the idea of
   reproducible, version controlled crowdsourcing pipelines and to make my own
   crowdsourcing research reproducible. I open sourced amti so that others could run my
   pipelines, to share the idea of reproducible

There should be one at least in C#, people shouldn't need to always roll their own solutions for this.