Conversation
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
Commits
|
|
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-06-16T20:34:31.717Z |
melissag-ensemble
approved these changes
Jun 16, 2026
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
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.
This sets our pages to explictly be utf-8. Normally our pages already set to uft-8 by default but in AdobeDocsPrivate, it seems to set it to a legacy charset:
'windows-1252'which is causing some rendering issues.This is a little hard to test since our pages are all on utf-8 but if you look at:
https://charset--adp-devsite-stage--adobedocs.aem.page/app-builder/docs/intro_and_overview/
And inspect the head, you should see a value:
After we merge this into prod, we can test the other pages (https://developer-stage.adobe.com/autocrop-api/api/#operation/facadeJobStatus or https://developer-stage.adobe.com/harmonize-image/api/#operation/harmonizeAsync) and see if it fixes the rendering issues