7c9eece09a
Some checks failed
Backend API CI / test-unit (push) Has been cancelled
Backend API CI / test-integration (push) Has been cancelled
Veza CI / Rust (Stream Server) (push) Has been cancelled
Veza CI / Backend (Go) (push) Has been cancelled
Veza CI / Notify on failure (push) Has been cancelled
Veza CI / Frontend (Web) (push) Has been cancelled
Frontend CI / test (push) Has been cancelled
Security Scan / Secret Scanning (gitleaks) (push) Has been cancelled
First-attempt commit02728909fonly captured the .gitignore change; the pre-commit hook silently dropped the 343 staged moves/deletes during lint-staged's "no matching task" path. This commit re-applies the intended J1 content on top of24af2f72b(which was pushed in parallel). Uses --no-verify because: - J1 only touches .md/.json/.log/.png/binaries — zero code that would benefit from lint-staged, typecheck, or vitest - The hook demonstrated it corrupts pure-rename commits in this repo - Explicitly authorized by user for this one commit Changes (343 total: 169 deletions + 174 renames): Binaries purged (~167 MB): - veza-backend-api/{server,modern-server,encrypt_oauth_tokens,seed,seed-v2} Generated reports purged: - 9 apps/web/lint_report*.json (~32 MB) - 8 apps/web/tsc_*.{log,txt} + ts_*.log (TS error snapshots) - 3 apps/web/storybook_*.json (1375+ stored errors) - apps/web/{build_errors*,build_output,final_errors}.txt - 70 veza-backend-api/coverage*.out + coverage_groups/ (~4 MB) - 3 veza-backend-api/internal/handlers/*.bak Root cleanup: - 54 audit-*.png (visual regression baselines, ~11 MB) - 9 stale MVP-era scripts (Jan 27, hardcoded v0.101): start_{iteration,mvp,recovery}.sh, test_{mvp_endpoints,protected_endpoints,user_journey}.sh, validate_v0101.sh, verify_logs_setup.sh, gen_hash.py Session docs archived (not deleted — preserved under docs/archive/): - 78 apps/web/*.md → docs/archive/frontend-sessions-2026/ - 43 veza-backend-api/*.md → docs/archive/backend-sessions-2026/ - 53 docs/{RETROSPECTIVE_V,SMOKE_TEST_V,PLAN_V0_,V0_*_RELEASE_SCOPE, AUDIT_,PLAN_ACTION_AUDIT,REMEDIATION_PROGRESS}*.md → docs/archive/v0-history/ README.md and CONTRIBUTING.md preserved in apps/web/ and veza-backend-api/. Note: The .gitignore rules preventing recurrence were already pushed in02728909fand remain in place — this commit does not modify .gitignore. Refs: AUDIT_REPORT.md §11
61 lines
1.9 KiB
Markdown
61 lines
1.9 KiB
Markdown
# Fix Visuel Radical - Mode Clean
|
|
|
|
## Corrections Appliquées
|
|
|
|
### 1. Scanlines Complètement Désactivées
|
|
- `body::after` est maintenant `display: none !important`
|
|
- Tous les effets de scanlines sont désactivés
|
|
|
|
### 2. Bordures Verticales Supprimées
|
|
- Toutes les bordures verticales (`border-left`, `border-right`) supprimées
|
|
- Exception pour les inputs de formulaire
|
|
- Bordures supprimées sur tous les pseudo-éléments
|
|
|
|
### 3. Détection des Éléments sur le Bord Droit
|
|
- Détection automatique des éléments positionnés sur le bord droit
|
|
- Masquage automatique des éléments suspects (< 10px de largeur)
|
|
|
|
### 4. Overflow Masqué
|
|
- `overflow-x: hidden` sur `html` et `body`
|
|
- Empêche tout débordement horizontal
|
|
|
|
## Outils de Diagnostic
|
|
|
|
Dans la console du navigateur (F12), vous pouvez utiliser :
|
|
|
|
### Mode Clean (Désactive TOUS les effets visuels)
|
|
```javascript
|
|
__enableCleanMode() // Active le mode clean
|
|
__disableCleanMode() // Désactive le mode clean
|
|
```
|
|
|
|
### Trouver les Lignes Verticales
|
|
```javascript
|
|
__findVerticalLines() // Trouve et surligne tous les éléments suspects
|
|
__inspectVerticalLine() // Inspecte visuellement les lignes
|
|
```
|
|
|
|
## Instructions de Test
|
|
|
|
1. **Recharger avec cache vide** : `Ctrl+Shift+R` (ou `Cmd+Shift+R` sur Mac)
|
|
2. **Si la ligne persiste**, ouvrir la console (F12) et exécuter :
|
|
```javascript
|
|
__enableCleanMode()
|
|
```
|
|
Cela désactivera TOUS les effets visuels pour isoler le problème.
|
|
|
|
3. **Identifier l'élément problématique** :
|
|
```javascript
|
|
__findVerticalLines()
|
|
```
|
|
Cela surlignera tous les éléments suspects.
|
|
|
|
## Si le Problème Persiste
|
|
|
|
Si même avec le mode clean la ligne est visible, cela signifie qu'elle vient d'un élément HTML spécifique, pas d'un effet CSS. Dans ce cas :
|
|
|
|
1. Utiliser `__findVerticalLines()` pour identifier l'élément
|
|
2. Inspecter l'élément dans les DevTools
|
|
3. Noter le tag, l'ID, et les classes de l'élément
|
|
4. Partager ces informations pour un fix ciblé
|
|
|