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
This is only a problem in Firefox. If a query string is appended to the URL for an image then it is possible that Firefox version 88.0 will think it is broken. This is not a problem in Chrome (90.x) or Edge (90.x), neither IE nor Opera have been tested.
Will show the right width but lose the bottom half of the image on Firefox, the image is properly sized. If this is inline with other content, part of an anchor link and so on then Firefox will fallback to broken image rendering, the alt text, or the broken image icon.
This may relate to particular ratios of the original and the query string is an added problem for Firefox, Chrome in general seems to ignore the original URI and just renders the result.
As using width= avoids the problem this is just information.
The text was updated successfully, but these errors were encountered:
This is only a problem in Firefox. If a query string is appended to the URL for an image then it is possible that Firefox version 88.0 will think it is broken. This is not a problem in Chrome (90.x) or Edge (90.x), neither IE nor Opera have been tested.
Using the width= attribute avoids the problem.
For example:
https://assets.zettel.io/public/00000000-8b0b92d0-c7ed-461b-ac3f-7896536e03ea/image27.png?200
Will show the right width but lose the bottom half of the image on Firefox, the image is properly sized. If this is inline with other content, part of an anchor link and so on then Firefox will fallback to broken image rendering, the alt text, or the broken image icon.
This may relate to particular ratios of the original and the query string is an added problem for Firefox, Chrome in general seems to ignore the original URI and just renders the result.
As using width= avoids the problem this is just information.
The text was updated successfully, but these errors were encountered: