Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[web] Document viewport-fit=cover SafeArea support, URL percent-encoding preservation, and clean up web overview docs for Flutter 3.50

Aperta
  • Qualcosa non va?
#13,962 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kevmoo ci sta già lavorando.

Dal 16/10/2026.

  • #13986 di @kevmoo — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
56/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
dart, flutter
Ambito
documentation

Direzione di ricerca

Start with the named files under sites/docs/src/content/deployment/web/, release/breaking-changes/, platform-integration/web/, and resources/architectural-overview.md; review the referenced Flutter changes and the existing surrounding documentation. Update the pages and remove the unused link definitions as specified, then run the website’s documentation checks. Done means the Flutter 3.50 behavior and migration guidance are accurate and the outdated prose and broken link are fixed.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

a.rn.breaking-changes a.rn.release-notes d.enhancement dev.deployment dev.integration e1-hours from.team p1-high target.web
Page URL
Describe the problem

Flutter 3.50 includes two web platform behavior changes (viewport-fit=cover SafeArea support and URL percent-encoding preservation) plus several outdated/broken web architecture statements on docs.flutter.dev (cc @parlough @sfshaza2):

  1. viewport-fit=cover SafeArea support & layout breaking change: In Flutter 3.50 (flutter/flutter#191647), Flutter Web respects viewport-fit=cover in <meta name="viewport"> and populates FlutterView.viewPadding / MediaQuery.paddingOf / SafeArea from CSS env(safe-area-inset-*). Existing web apps that already had viewport-fit=cover in web/index.html (previously stripped by the engine) will now render edge-to-edge under notches and home indicators unless wrapped in SafeArea.
  2. Browser history URL percent-encoding preservation: URLs passed to SystemNavigator.routeInformationUpdated are no longer percent-decoded before being written to browser history (flutter/flutter#189835), preserving %2F, %26, %23, and %20 across page refreshes.
  3. Outdated 2019 HTML renderer prose & broken [hot reload behind a flag][] link: sites/docs/src/content/platform-integration/web/index.md#L30-L41 still describes the removed Dart-implemented HTML drawing layer, and sites/docs/src/content/resources/architectural-overview.md#L1084 contains an unresolved [hot reload behind a flag][] reference link.
Detailed page breakdown & affected targets (AI-assisted)
Expected fix
1. sites/docs/src/content/deployment/web.md & sites/docs/src/content/release/breaking-changes/
  • Edge-to-edge mobile web rendering (viewport-fit=cover):
    • Document how adding viewport-fit=cover to <meta name="viewport"> in web/index.html (now included as a commented-out option in flutter create templates) enables full-bleed edge-to-edge rendering on iOS and Android browsers and populates FlutterView.viewPadding / SafeArea via CSS env(safe-area-inset-*) (flutter/flutter#191647).
    • Add a breaking-change migration guide page under sites/docs/src/content/release/breaking-changes/ (and index it under Flutter 3.50 in sites/docs/src/content/release/breaking-changes/index.md) warning that existing web apps that already had viewport-fit=cover in web/index.html will now render under device cutouts/notches unless UI content is wrapped in SafeArea (or viewport-fit=cover is removed).
  • Browser history percent-encoding:
    • Note that EngineFlutterWindow (handleNavigationMessage) no longer calls Uri.decodeComponent on the uri string passed to SystemNavigator.routeInformationUpdated before calling browserHistory.setRouteName (flutter/flutter#189835), preventing loss of percent-encoded delimiters (%2F, %26, %23, %20) in route paths and query parameters.
2. sites/docs/src/content/platform-integration/web/index.md (https://docs.flutter.dev/platform-integration/web)
  • Rewrite ## How it works (L30-L41) to remove 2019 HTML-renderer prose ("We implemented the core drawing layer completely in Dart and used Dart's optimized JavaScript compiler...") and accurately describe compilation to JavaScript (dart2js / ddc) or WebAssembly (dart2wasm) paired with hardware-accelerated WebGL/WebGPU rendering via CanvasKit and Skwasm.
3. sites/docs/src/content/resources/architectural-overview.md (https://docs.flutter.dev/resources/architectural-overview)
Lingua principale
Dart
Stelle
3.1k
Fork
3.5k
Merge medio
2g 3h
PR unite (30g)
46

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di flutter/website

Tutte le issue di flutter/website

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.