You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In FunctionalTableData, when the contextual actions are being created, we can determine if the cell is this height and instead return a pre-rendered (and likely cached) image that includes both the text and the image. This might be a configurable property to allow it to be opted in or out.
This could have some side effects in scenarios where the cell changes size while the action is visible (device rotation, tableview gets wider).
The text was updated successfully, but these errors were encountered:
This could have some side effects in scenarios where the cell changes size while the action is visible (device rotation, tableview gets wider).
What I've done in the past is simple set editing for the cell to false in those scenarios, which returns the cell back to the normal state without the contextual actions visible. I would argue that this solution is satisfactory in most cases; likelihood of the cell changing height without a rotation is small for most use cases.
Likewise, check an app like Messages.app. Swipe to reveal actions and then rotate your device to landscape or vice versa 💩
http://www.openradar.me/33107135
In FunctionalTableData, when the contextual actions are being created, we can determine if the cell is this height and instead return a pre-rendered (and likely cached) image that includes both the text and the image. This might be a configurable property to allow it to be opted in or out.
This could have some side effects in scenarios where the cell changes size while the action is visible (device rotation, tableview gets wider).
The text was updated successfully, but these errors were encountered: