Repository navigation
Validate CodeCogs PNGs and prevent low-resolution fallbacks - #75
Merged
Merged
Conversation
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.
CodeCogs error artwork can arrive as HTTP 200 and pass our fixed PNG-prefix checks, allowing a rejected
dpicommand to appear in an equation. Validate CodeCogs' structured PNG response and insert those exact bytes, including in Slides. Skip the low-resolution GIF and unavailable staging fallbacks while retaining their legacy de-render links. Keep 900-DPI PNG sizing unchanged.Human intent
dpi900errors and improve CodeCogs output quality.Evidence and validation
9cb82d4, three new tests failed: HTTP 200 error artwork accepted, unvalidated responses accepted, and GIF/staging fallback attempted. An Inspector breakpoint confirmed Common marked the captured unknown-dpi PNG successful.--lib es2018,dom --skipLibCheck(the default configuration has existing DOM/type-library conflicts).The historical upstream trigger that mishandled a correctly braced DPI command remains unproven. Fixtures reproduce acceptance of the visible error artwork, not that upstream event. The exact angle example was not found in searched production logs. Host APIs are mocked in unit tests; this is not a live Google insertion test. No deployment performed.
Stacked on #74. Tracks AGENTS-250.