When the component is added to a record view page, either in the default rendered section or in a tab, it initialises correctly for the first record viewed, but the second record onwards the canvas doesn't resize and the touch events aren't received. This happens when embedding directly as a lightning component or a flow.
Upon investigation, while the underlying HTML elements appear on the page and can be located by the component JavaScript, they report sizes of zero and attempts to set attributes while appearing successful have no effect.
keirbowden
commented
3 years ago
When the component is added to a record view page, either in the default rendered section or in a tab, it initialises correctly for the first record viewed, but the second record onwards the canvas doesn't resize and the touch events aren't received. This happens when embedding directly as a lightning component or a flow.
Upon investigation, while the underlying HTML elements appear on the page and can be located by the component JavaScript, they report sizes of zero and attempts to set attributes while appearing successful have no effect.
The workaround for this is to use the Quick Action approach, as detailed at : https://bobbuzzard.blogspot.com/2016/11/lightning-component-actions-with.html