Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify M3 demo sample issues, determine source of each, and file relevant issues #2129

Open
8 of 25 tasks
parlough opened this issue Dec 23, 2023 · 2 comments
Open
8 of 25 tasks
Assignees

Comments

@parlough
Copy link
Member

parlough commented Dec 23, 2023

I'm going to be using this issue to find and track issues with the sample, then determine if they're caused by wasm compilation, skwasm, the sample itself, browser support, or Flutter. If an issue is not open for any issues found, I will open one in the appropriate repository and link to it from here.

Code: https://github.com/flutter/samples/tree/main/material_3_demo
Version: HEAD on main
Staged: https://parlough-testing-skwasm.web.app/

Determined issues

Wasm build

These issues happen with flutter build web --wasm (using CanvasKit).

skwasm renderer

These issues happen with flutter build web --wasm --web-renderer=skwasm.

Flutter (framework or engine)

I determined these issues affect all Flutter backends, at least web and desktop.

Sample

I determined these issues are likely because of the sample itself.

  • Tab order in wide screen/expanded navigation menu is wrong.
    • It seems to be going by column rather than row?
  • In the search anchor search view, "No search history" is too low contrast and positioned too close to the divider.
  • If you open "Show bottom sheet" then close it by dragging or the back button in the upper right, the text button will still say "Hide bottom sheet" despite it already being hidden.
  • In the "Text fields" section, the X/close buttons added to each should only appear once text is added and they should have a little margin from the right.

Browser(s)

  • Annoying warning about WebGL extension support from Chrome
    • WebGL: this extension has very low support on mobile devices; do not rely on it for rendering effects: WEBGL_polygon_mode

Undetermined issues

Not sure

  • Uncaught TypeError: Cannot read properties of null (reading 'ds'...
    • I can't reproduce. Might have been fixed.
  • Still working to find more discrepancies
  • Typing in text input boxes on narrow, short screen moves page up

Sample or Flutter

I determined these issues impact the sample whether running with Wasm or not. I still need to determine if they are because of Flutter or because of the sample.

@parlough parlough self-assigned this Dec 24, 2023
@parlough parlough changed the title Fix m3 demo issues when running with wasm and skwasm Identify M3 demo sample issues, determine source of each, and file relevant issues Jan 11, 2024
@flutter flutter deleted a comment from domesticmouse Jan 11, 2024
@parlough
Copy link
Member Author

parlough commented Jan 11, 2024

Hi all! I've gone through the Material 3 demo sample to find various issues, then determine if they are caused by dart2wasm compilation, the skwasm renderer, Flutter, or the sample itself.

You can find each of these issues above organized within those categories. Each issue has a link to the corresponding Flutter or Dart issue(s) I filed for them, as well as to the relevant fix if that's been made.

\cc @kevmoo For awareness about the various skwasm issues. As for dart2wasm with or without skwasm, it resulted in only one issue unique to it, and I was able to fix that in the SDK.
\cc @QuncCccccc For awareness and potentially help with resolving the sample and framework issues.

Thanks!

@kevmoo
Copy link
Contributor

kevmoo commented Jan 11, 2024

@parlough – you rock SOOO MUCH 🤘

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants