| Auto-Submit | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
navigationController->_syncEncryptionPassphraseTableViewController =We should avoid doing that. I guess it should be a property.
SyncEncryptionPassphraseTableViewController* controller =Why do you use `_syncEncryptionPassphraseTableViewController`? I would imagine the CHECK in line 1316 should fail?
@property(weak, nonatomic)We usually put nonatomic before weak.
@protocol SyncEncryptionPassphraseTableViewControllerPresentationDelegateThis should inherit from `NSObject`.
if (_settingsAreDismissed) {So I guess with your changes this method will often be called twice. I think this is not really a problem. But we can remove the comment now?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +0 |
controllerToPush = _syncEncryptionTableViewController =There is an issue here. You set `_syncEncryptionTableViewController` but we never set it to nil. Therefore, with your patch, it is not possible to open twice `SyncEncryptionTableViewController`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
controllerToPush = _syncEncryptionTableViewController =There is an issue here. You set `_syncEncryptionTableViewController` but we never set it to nil. Therefore, with your patch, it is not possible to open twice `SyncEncryptionTableViewController`.
Oh, you are right. I remove the early return for `_syncEncryptionTableViewController` then. It’ll be in a different CL, this one is already big enough I believe
navigationController->_syncEncryptionPassphraseTableViewController =We should avoid doing that. I guess it should be a property.
Done
SyncEncryptionPassphraseTableViewController* controller =Arthur MilchiorWhy do you use `_syncEncryptionPassphraseTableViewController`? I would imagine the CHECK in line 1316 should fail?
I assume your question was expected to be "Why don’t you use". Appart from that, you’re quite right, thanks.
@property(weak, nonatomic)We usually put nonatomic before weak.
Done
@protocol SyncEncryptionPassphraseTableViewControllerPresentationDelegateThis should inherit from `NSObject`.
Done
if (_settingsAreDismissed) {So I guess with your changes this method will often be called twice. I think this is not really a problem. But we can remove the comment now?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
SyncEncryptionPassphraseTableViewController* controller =Arthur MilchiorWhy do you use `_syncEncryptionPassphraseTableViewController`? I would imagine the CHECK in line 1316 should fail?
I assume your question was expected to be "Why don’t you use". Appart from that, you’re quite right, thanks.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[iOS]Add a delegate to sync encryption view
If the sync encryption view is opened twice quickly (with a double tap),
and `settingsWillBeDismissed` is called on the first ViewController,
`viewDidLoad` will be executed after the `settingsWillBeDismissed`,
causing for a crash due to access to `self.browser` which became null.
By ensuring that the view is only opened once, this crash is avoided.
There is still the issue that if we simultaneously dismiss this view and
tap on the account menu, the account menu get closed.
However, it’s not clear it’s related, and at least, now, we have a
closed menu instead of an access to a null pointer.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |