- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper presents AesCode, a framework for generating HTML visual artifacts from content prompts and generated reference images. It uses a design graph to separate content requirements from visual cues and construct complementary rewards. Qwen3-VL models are trained through SFT followed by reinforcement learning with per-channel reward normalization. Evaluation on a new 300-prompt benchmark and three external benchmarks show improvements in content correctness and visual quality over the base models, with visual quality comparable to the evaluated frontier models.
Critical strengths
-
Thorough evaluation. The paper tests diverse open-source and proprietary models, trains both 8B and 32B variants, and includes ablations, external benchmarks, and human evaluation.
-
Gains persist without reference images. Removing the reference at inference reduces AesCode-8B’s Visual score by only 1.0 point, supporting its usefulness in prompt-only generation.
Critical weaknesses
1. The evaluation does not directly test selective use of noisy references. A central premise is that generated references may contain incorrect text or data, so AesCode should borrow their design while following the prompt’s content requirements. However, the experiments mainly assess overall correctness and visual quality, without directly testing whether the model rejects erroneous reference content when it conflicts with the prompt.
2. The handling of conflicting reward signals is unclear. Text and Table/Chart rewards enforce prompt-derived requirements, while Semantic Layout, Whitespace, and VGR reward reference-derived properties. These objectives can conflict when correcting content requires changing the layout—for example, adding an element omitted from the reference. The paper should clarify how such conflicts are resolved.
Questions for authors
How does AesCode behave on references with content errors? how are reference-derived graph constraints and rewards adjusted to avoid penalizing correct outputs?
3 comments
Dear Reviewer Q3h3, thank you again for your detailed review. Following your suggestion, the General Response and our reply now test the conflict points directly on a controlled set of 391 inputs, explain how each reward channel treats a conflict so that correct outputs are not penalized, and add this study to Appendix C.4 of the revised paper. We would be grateful if you could let us know whether this resolves your concerns, and we would welcome the chance to address any remaining questions.
Thanks for your efforts in addressing the concerns provided. I have increased my score accordingly.
Response to Reviewer Q3h3
We sincerely thank the reviewer for the detailed and thoughtful review, and for recognizing the thoroughness of the evaluation and that the gains persist without the reference at inference.
The three points concern the same question, so we answer them together. We ran a full study on such conflicts, reported in the General Response (G1–G4), and summarize below the parts relevant to W2 and then W1.
1. How the reward channels handle a conflict (W2, and the second part of Q)
Only two channels compare the output with the reference. VGR is not purely reference-derived, since its design graph and questions follow the prompt wherever it specifies content or structure, and take only layout and visual style from the reference.
Reward channels at a conflict point (G2, Tables 2 and 3).
2. How the trained model behaves on conflicts (W1, and the first part of Q)
Noisy references are already part of our evaluation. The G1 audit finds natural conflicts in 19.7% of all samples, the benchmark included, and all reported results include them. Following the reviewer's suggestion, we also test the conflict point directly on a controlled set of 391 inputs (G3, examples in Fig. C2).
We have added the controlled conflict study and these examples to Appendix C.4 (Table C2, Figs. C2 and C3), and stated the source of each reward channel in §3.2 (marked in blue). We hope this study addresses the reviewer's concerns, and would be grateful if the reviewer would take it into account in the final assessment.