Availability of self-contained HTML used to generate DiffSpot
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- data
Research direction
Start by checking the Hugging Face release and the repository for references to the released benchmark pairs or regenerated HTML. The issue is complete when the availability or release plan for the corresponding self-contained HTML is clearly documented.
Written by the indexing model from the issue text.
Description
The paper states that each retained screenshot is paired with self-contained HTML produced through LLM regeneration, and that the CSS mutation pipeline operates directly on this static HTML.
I can find the before/after images and structured mutation metadata in the Hugging Face release, but I haven’t been able to locate the corresponding regenerated HTML.
Is the self-contained HTML corpus (or at least the HTML corresponding to the released 4,400 benchmark pairs) publicly available or planned for release?
We’re interested in using the code → render → mutation correspondence for advancing vision pipeline harnesses. We could create a mutator in like kindness to generate similar data, but then we would lose the existing 'exact benchmark' compatibility with your already established results.
Thanks,
Aaron
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Tencent/DiffSpot
All issues in Tencent/DiffSpot
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Add .devin pluginOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ayghri/i-have-adhd#249 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelscope/FunASR#3762 ·
Maintainers usually reply within 1 day