[6.x] Make SVG dimensions integers so in the meta data you see a nice number

[JayGeorge]

Description of the Problem

SVGs can sometimes show as having floating decimals in the asset browser, like this:

What this PR Does

Forces an integer like this:

How to Reproduce

1. Upload a bunch of SVGs and check them out in the asset browser - one of them will probably have a floating number

[Copilot]

Pull request overview

This PR modifies how SVG dimensions are stored and displayed in Statamic's asset management system, converting floating-point values to integers for cleaner presentation in the asset browser metadata.

Changes:

• Modified PHP backend to cast SVG width/height to integers when parsing from both SVG attributes and viewBox
• Added Math.floor() to JavaScript frontend to ensure dimensions display as integers in the asset editor

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
src/Imaging/Attributes.php	Updated svgAttributes() method to cast width and height values to integers using (int) instead of (float) for both direct attributes and viewBox parsing
resources/js/components/assets/Editor/Editor.vue	Added Math.floor() to width and height values in the asset dimensions badge display

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Casting SVG dimensions directly to int truncates decimal values, which can lose precision. For example, 30.5 becomes 30, and 29.9 becomes 29. Consider using round() instead of (int) to round to the nearest integer, which would be more accurate. This affects SVG files that have decimal dimensions in their width/height attributes.

[Copilot]

Casting viewBox dimensions directly to int truncates decimal values. For example, if a viewBox is "0 0 100.5 200.8", the dimensions will become 100 and 200 instead of 101 and 201. Consider using round() instead of (int) to round to the nearest integer for more accurate dimensions.

[Copilot]

The PHP code uses truncation with (int) cast while the JavaScript uses Math.floor(). While Math.floor() always rounds down toward negative infinity, the (int) cast in PHP truncates toward zero. For positive numbers they behave the same, but this inconsistency could cause confusion. Consider using floor() in PHP to match the JavaScript behavior, or preferably use round() in both places for more accurate rounding.

Suggested change

	<ui-badge pill v-if="asset.width && asset.height" icon="assets" :text="__('messages.width_x_height', { width: Math.floor(asset.width), height: Math.floor(asset.height) })" />
	<ui-badge pill v-if="asset.width && asset.height" icon="assets" :text="__('messages.width_x_height', { width: Math.round(asset.width), height: Math.round(asset.height) })" />

[Copilot]

The existing test expects floating-point values for SVG dimensions when width and height attributes are present (line 120 expects 30.0 and 60.0). This PR changes the code to return integers, which will break this test. The test file at tests/Assets/AttributesTest.php will need to be updated to expect integers instead of floats.

[jasonvarga]

I think we should leave the floats in PHP and just do the rounding in JavaScript.

You should use Math.round() so it rounds in the right direction. Math.floor() rounds down.

If you undo the PHP changes you can ignore all the copilot suggestions.