[Bug - Partner Center] Localized listing descriptions report success but do not persist

Describe the bug

When editing localized Microsoft Edge Add-ons listings in Partner Center, Save draft can display “Draft saved successfully” even though the description was not persisted. After closing the editor and reloading the page, the language row is still marked Incomplete and the description is Empty.

The previous success notification can also remain visible after opening another locale, making an unsuccessful save look successful.

To Reproduce

1. Open an Edge extension in Partner Center that contains many localized listings.
2. Go to Store listings and edit a language.
3. Enter a valid localized description of more than 250 characters and below the advertised 10,000-character limit.
4. Click Save draft and observe “Draft saved successfully”.
5. Close the editor and reload the Store listings page.
6. Observe that the language may still be marked Incomplete and its description is Empty.
7. Repeat with multiple locales and observe that an earlier success notification can remain visible on the next locale page.

In one reproducible case, a Japanese description of 480 characters (approximately 1,246 UTF-8 bytes) did not persist. A shorter version of 330 characters (approximately 830 UTF-8 bytes) did persist. This suggests an undocumented byte-size limit, serialization issue, or backend validation failure.

Expected behavior

• “Draft saved successfully” should only appear after the server has persisted the description.
• Any payload or byte-size limit should be documented and validated before saving.
• A failed save should display a clear error.
• Notifications and form state should not carry over between locales.
• The listing row should reliably reflect the saved server state.

Additional observed problems

• The locale form sometimes took 10–15 seconds to become usable.
• Returning to the Store listings table sometimes took more than 20 seconds.
• Hidden or stale form elements remained present during navigation.
• An Action Center panel unexpectedly covered the listings table. Edit buttons remained visible and appeared enabled but did not respond.
• Browser console errors included Failed to fetch.
• Partner Center also logged a JSON parsing error resembling Unexpected token ... PNG ... is not valid JSON while processing an extension logo duplicated across languages.
• The mandatory certification-notes field only became visible after clicking Publish.

Impact

While preparing 51 localized listings, many descriptions had to be entered and saved repeatedly. This creates a serious risk of unknowingly submitting incomplete listings. All 51 languages were eventually completed only by shortening affected descriptions, waiting between operations, and verifying every row after a full reload.

Desktop

• OS: macOS
• Browser: Chromium-based desktop browser
• Partner Center date tested: 28 August 2026
• Extension package version: 1.23.0

Additional context

The extension was ultimately submitted successfully. This report concerns the reliability and validation of the Partner Center listing workflow, not the extension’s runtime behavior.