Correct imap buttons on servers page & trigger change sieve_mode_tls checkbox on edit server

[Shadow243]

Follow up to #1199 & #1266

[mercihabam]

@Shadow243 I am skeptical as to why the pipeline succeeded here while containing mistakes to the test, showing up in follow-up pull requests. Does the pipeline run on cached content?

[Shadow243]

@Shadow243 I am skeptical as to why the pipeline succeeded here while containing mistakes to the test, showing up in follow-up pull requests. Does the pipeline run on cached content?

It's weird, this test doesn't work sometimes, I even opened another PR #1290 to fix this, with the same fix you applied my test didn't pass. let's see if it won't break anymore.

[mercihabam]

@Shadow243 I am skeptical as to why the pipeline succeeded here while containing mistakes to the test, showing up in follow-up pull requests. Does the pipeline run on cached content?

It's weird, this test doesn't work sometimes, I even opened another PR #1290 to fix this, with the same fix you applied my test didn't pass. let's see if it won't break anymore.

As for the test, it is stable. Reintroducing the line self.wait_for_navigation_to_complete() worked for you as well, but you encountered a separate test failure that was fixed with this change.

It is still confusing that the pipeline sometimes runs against old content (seemingly from the master branch) rather than the actual branch state.

[Shadow243]

@Shadow243 I am skeptical as to why the pipeline succeeded here while containing mistakes to the test, showing up in follow-up pull requests. Does the pipeline run on cached content?

It's weird, this test doesn't work sometimes, I even opened another PR #1290 to fix this, with the same fix you applied my test didn't pass. let's see if it won't break anymore.

As for the test, it is stable. Reintroducing the line self.wait_for_navigation_to_complete() worked for you as well, but you encountered a separate test failure that was fixed with this change.

It is still confusing that the pipeline sometimes runs against old content (seemingly from the master branch) rather than the actual branch state.

Super, i then close #1290. We will find out what is making pipeline to run against old content.