docs: trim transparent padding from v22 event hero image#69156
Open
erkamyaman wants to merge 1 commit into
Open
docs: trim transparent padding from v22 event hero image#69156erkamyaman wants to merge 1 commit into
erkamyaman wants to merge 1 commit into
Conversation
Contributor
Author
|
We saved 222kb so not too bad I suppose, every byte counts :) |
Contributor
Author
|
Mobile before: after: |
MarkTechson
requested changes
Jun 4, 2026
Contributor
MarkTechson
left a comment
There was a problem hiding this comment.
We can keep the image change, but remove the text change.
The v22 event hero PNG shipped with a wide transparent margin baked into
its 960x540 canvas. Under the shared `img { width: 100% }` rule that empty
border stretched along with the artwork, leaving visible space around the
image. Trims the canvas to the artwork bounds (831x473) so it renders
flush; the retained pixels are unchanged and the file shrinks from about
795 KB to 568 KB.
1222cc5 to
6725608
Compare
Contributor
Author
|
Updated everything as you suggested. Thank you! @MarkTechson |
MarkTechson
approved these changes
Jun 4, 2026
Contributor
MarkTechson
left a comment
There was a problem hiding this comment.
LGTM
Thanks for taking the time
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v22 event hero PNG shipped with a wide transparent margin baked into its 960x540 canvas. Under the shared
img { width: 100% }rule that empty border stretched along with the artwork, leaving visible space around the image that the v21 hero does not have. Trims the canvas to the artwork bounds (831x473) so it renders flush; the retained pixels are unchanged.PR Checklist
Please check that your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The v22 event hero PNG (
angular-v22-hero.png) ships as a 960x540 canvas with a wide transparent margin baked around the artwork. Because content images render atwidth: 100%, that empty border stretches with the image and shows up as visible space around the hero.What is the new behavior?
The hero PNG is trimmed to the artwork bounds (831x473), so it renders flush with no surrounding gap. The retained pixels are unchanged (verified identical, lossless crop), and file size drops from ~795 KB to ~568 KB.
Does this PR introduce a breaking change?