fix(ui): troca text-rendering pra optimizeLegibility - #38
Merged
Conversation
geometricPrecision deixa o texto com aparencia borrada em navegadores Chromium, mais perceptivel em texto pequeno/baixo contraste (ex: descricoes dos cards em text-site-body-muted). optimizeLegibility mantem o kerning bom sem esse efeito. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Blocos html.light que so redeclaravam a mesma custom property que ja muda de valor sozinha via :root/html.light (navbar, prefs-panel, body, article h2/h3/blockquote, hovers de link de heading, code block do artigo) - zero diferenca de renderizacao, confirmado via toggle de tema real no preview - a.link: classe morta (sem nenhum uso em src/app/content), cor hardcoded em white que quebraria o tema claro se algum dia fosse usada Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
.interactive-card, .interactive-row e .about-tag mantinham will-change: transform o tempo todo, mesmo sem interacao - forcando uma camada de composicao permanente em cada elemento com essas classes. Como sao usadas em listas longas (jogos, artistas, repos, tags), isso desperdicava GPU/memoria a toa. Move a declaracao pra dentro do :hover/:focus-within, que e quando a transform de fato acontece. Deixei de fora os !important em .content pre/pre code - confirmei que sao necessarios pra sobrepor os estilos inline que o Shiki injeta no HTML do syntax highlighting. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Continuacao do PR #37 (ja mergeado antes deste commit ser pushado).
text-rendering: geometricPrecisionnobodydeixava o texto com aparenciaborrada em navegadores Chromium — mais perceptivel em texto pequeno/baixo
contraste (ex: descricoes dos cards em
text-site-body-muted, 11-14px).Troca pra
optimizeLegibility, que mantem o kerning bom sem esse efeito.Test plan
getComputedStyle(document.body).textRenderingconfirmado comooptimizelegibilityno previewyarn prettier --check styles/globals.csslimpo (sem stylelint configurado no projeto)