github-actions[bot]
commented
2 months ago This issue has been labeled as a bug since it was created using the 🚨 Bug Report Template.
Hi there, thank you so much for the report!
Following our Maintenance Process, we will review your bug report and get back to you next Wednesday. To ensure a smooth review of your issue and avoid unnecessary delays, please make sure your issue includes the following:
- Information about your environment and packages you use (Node.js version, package names and their versions, etc.)
Feel free to attach a copy of your
package.jsonfile. - Any troubleshooting steps you already went through
- A minimal reproduction of the issue, and/or instructions on how to reproduce it
If you have identified the cause of the bug described in your report and know how to fix it, you're more than welcome to open a pull request address it. Check out our quick start guide for a simple contribution process.
If you think your issue is a question (not a bug) and would like quicker support, please close this issue and forward it to an appropriate section on our community forum: https://community.prismic.io
- The Prismic Open-Source Team
When using
<PrismicNextImage />with thewidthprop defined but without specifying aheight, the resolved height may result in a floating-point value, which doesn't follow the html spec and triggers errors when you run it throught https://validator.w3.org/nu/.Versions
@prismicio/next: v1.6.0next: v14.2.7Reproduction
Upload an image with 128x37 px size in Prismic and use it with
<PrismicNextImage field={image} width={110} />.Steps to reproduce
Check the img element in dev tools or validate the page to https://validator.w3.org/nu/.
What is expected?
Resolved height should always be a non-negative integer.
What is actually happening?
The height isn't always an integer, depending on the width/ar it can be a floating-point number.