search

dart-lang / dart-pad

An online Dart editor with support for console, web, and Flutter apps
https://dartpad.dev
BSD 3-Clause "New" or "Revised" License
1.71k stars 554 forks source link

Rendering problem in Chrome Canary #1395

Closed johnpryan closed 8 months ago

johnpryan commented 4 years ago
  1. Go to the exceptions code example in the cheatsheet codelab: https://dart.dev/codelabs/dart-cheatsheet#code-example-9
  2. Click the Solution tab and confirm that you want to show the solution.
  3. Copy the solution code. (Either select-all and copy on the keyboard or clicking the copy icon works.)
  4. Go back to the Dart tab, and select all the code. Paste the solution code into the Dart tab.

image

kwalrath commented 4 years ago

I can repro in Canary but not Stable Google Chrome. I also think it might be tied to problems in the solution code (https://github.com/dart-lang/site-www/issues/2118), since I tried the same steps with https://dart.dev/codelabs/dart-cheatsheet#code-example-5 and it didn't break.

kwalrath commented 4 years ago

I'm seeing a similar rendering issue for the iterables codelab, and I didn't even interact (much) with the code:

image

To reproduce, use Canary to go to https://mb-dart-dev-1.firebaseapp.com/codelabs/iterables#example-using-iterator-and-for-in-loop, and try to scroll the code. In a fresh window, I can't see anything below the top half of line 21, but the top matter IS appearing.

The console has nothing interesting (just a bunch of "DevTools failed to parse SourceMap" messages).

domesticmouse commented 4 years ago

I'd be interested to know if this failure is reproducible with Flutter for web. That way we know if it is a Flutter for web issue, or if it is something we are introducing in dart-pad and/or dart-services.

The version of Flutter that is deployed in the serving is https://github.com/flutter/flutter/tree/fbabb264e0ab3e090d6ec056e0744aaeb1586735, which is about 24 days behind master. We can bring it closer to head, but there are stability risks. We need to find a good PR to migrate to.

RedBrogdon commented 4 years ago

We've had rendering issues with Canary before (#914), and they didn't end up repro-ing after the Canary version made it to stable release.

Is it possible there's something intrinsic to the way the canary version is built that's throwing us off? Could we contact the Chrome team and get some advice here?

domesticmouse commented 4 years ago

It's also a problem in Chrome 79 (beta) which according to https://www.chromestatus.com/features/schedule is due to become stable in 13 days.

parlough commented 8 months ago

There haven't been more updates here since 2019 and the issues were appearing on nightly versions of Chrome, so I'm going to close this for now. If anyone experiences new issues with any supported browsers (latest 2 versions), please open a new issue with reproduction details. Thanks!