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
The standard width for BP email templates - and email templates in general - is 600px. Due to technical limitations in email clients, this is the widest width that's practical for cross-platform messages.
When an activity item included in a digest contains an image, and image dimensions (either explicit with width attribute or implicit via the original image width) are greater than 600px wide, it can expand the viewport in some clients - notwithstanding the max-width: 600px declaration on the email container.
I think we can avoid this by doing a bit of preprocessing magic when building the email markup. Namely:
Look for <img> elements
If an element doesn't have a width, or has width wider than 600, shrink to 600 (and remove height to avoid distortion)
I can work on a patch for this but first I wanted to get a sanity check from @r-a-y that this is a sensible way forward.
The text was updated successfully, but these errors were encountered:
The standard width for BP email templates - and email templates in general - is 600px. Due to technical limitations in email clients, this is the widest width that's practical for cross-platform messages.
When an activity item included in a digest contains an image, and image dimensions (either explicit with
width
attribute or implicit via the original image width) are greater than 600px wide, it can expand the viewport in some clients - notwithstanding themax-width: 600px
declaration on the email container.I think we can avoid this by doing a bit of preprocessing magic when building the email markup. Namely:
<img>
elementswidth
, or haswidth
wider than600
, shrink to600
(and removeheight
to avoid distortion)I can work on a patch for this but first I wanted to get a sanity check from @r-a-y that this is a sensible way forward.
The text was updated successfully, but these errors were encountered: