Fixed: 481648910How do you repro this bug on Canary ? When I add a long query it resizes and scrolls as expected.
[self commitUIUpdates];The UI is already updated in commitUIUpdates, why do we need to force a layout after ?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Fixed: 481648910How do you repro this bug on Canary ? When I add a long query it resizes and scrolls as expected.
Did you have a tab input context? That is the only way I can repro.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[self commitUIUpdates];The UI is already updated in commitUIUpdates, why do we need to force a layout after ?
because we need to update preferredContentSize. In this bug instance, nothing in commitUIUpdates triggers anything because it is just the text field changing, nothing else.
| 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. |
[self.consumer updatePreferredContentSizeForNewTextFieldHeight];What if you instead override the preferredContentSize to be a computed property instead
```
- (CGSize)preferredContentSize {
CGFloat inputHeight = [self inputHeight];
return CGSizeMake(self.view.bounds.size.width, inputHeight);
}
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
Chris LuThe UI is already updated in commitUIUpdates, why do we need to force a layout after ?
because we need to update preferredContentSize. In this bug instance, nothing in commitUIUpdates triggers anything because it is just the text field changing, nothing else.
Acknowledged
[self.consumer updatePreferredContentSizeForNewTextFieldHeight];What if you instead override the preferredContentSize to be a computed property instead
```
- (CGSize)preferredContentSize {
CGFloat inputHeight = [self inputHeight];
return CGSizeMake(self.view.bounds.size.width, inputHeight);
}
```
That doesn't solve anything here. We need to actually trigger a recalculation by ComposeboxViewController, which is done by triggering a relayout.
| 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. |
| Code-Review | +1 |
[self.consumer updatePreferredContentSizeForNewTextFieldHeight];Chris LuWhat if you instead override the preferredContentSize to be a computed property instead
```
- (CGSize)preferredContentSize {
CGFloat inputHeight = [self inputHeight];
return CGSizeMake(self.view.bounds.size.width, inputHeight);
}
```
That doesn't solve anything here. We need to actually trigger a recalculation by ComposeboxViewController, which is done by triggering a relayout.
Acknowledged
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Chris LuHow do you repro this bug on Canary ? When I add a long query it resizes and scrolls as expected.
Did you have a tab input context? That is the only way I can repro.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[ios] Force layout when composebox text field height changes
There is currently no signal that forces a recalculation of the
preferredContentSize. Calling layoutIfNeeded ensures the updated
text field height is factored in.
Setting the composebox input items should also require a recalculation
since it adds height to ComposeboxInputPlateViewController.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |