-
Notifications
You must be signed in to change notification settings - Fork 555
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
Console warnings in pages with embedded DartPads #791
Comments
The polymer components are out of date and will need to be updated in the near future. |
Thanks, @Georgehe4! @devoncarew please let us know when the changes go live, so I can close dart-lang/site-www#422. |
The changes should be live now. There will still be warnings but there will
be no impact on anything the users see in their browser.
Hopefully polymer will update their build process to remove the warnings
soon.
…On Mon, Mar 5, 2018 at 1:38 PM, Kathy Walrath ***@***.***> wrote:
Thanks, @Georgehe4 <https://github.com/georgehe4>!
@devoncarew <https://github.com/devoncarew> please let us know when the
changes go live, so I can close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#791 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADARlAmk-ShXV9nmgu2au8E5tbzf-o6gks5tbYX1gaJpZM4QaJvt>
.
|
Ah, OK, I'll leave dart-lang/site-www#422 open then. I currently see 4 browser warnings in https://www.dartlang.org/guides/get-started:
|
The deprecation notice deadline is approaching:
Any update on this. Btw, this impacts both https://www.dartlang.org and https://webdev.dartlang.org. |
Hey @chalin, the deprecation notices will be present until Polymer/polymer#4679 is addressed. The site will still function after the /deep/ combinator is removed. |
While it doesn't seem to break Dartpad, there are more errors now: (seen today on https://www.dartlang.org/guides/language/language-tour) As a first guess, this may be a result of some the changes I made in #826. Will investigate first thing Monday.
|
These might be connected to these other warnings on that same page:
|
Compilation failed warnings seem to be the result of some kind of initialization timing race. It's reproducible locally in the embedder_demo.html that loads Hello World, and results in the program not being correctly auto-run by the embedder. |
The Uncaught Errors on page load are caused by attempting to compile a gist that hasn't loaded yet, here: Line 102 in 4f3c839
|
Some of the remaining console warnings seem to be coming from codemirror. I've got a patch that seems to solve it but I want to look into getting it into upstream. The embedded-specific warnings I haven't looked at yet. |
The polymer warnings will persist until the new embed UI replaces the current embed UI. I'm not seeing any CodeMirror-related warnings at this point. |
Is this issue still relevant -- are the original warnings still being issued? |
@johnpryan swapped the new embed UI for the old one a while back, so there should no longer be any polymer code loading into anyone's browser. This should be closed at this point. |
Co-authored-by: Brett Morgan <[email protected]>
dart-lang/site-www#422 reports 3 Chrome console warnings in at least 4 pages, all of which have embedded DartPads. (No warnings appear in other, non-DartPad-containing pages that I've spot checked, such as www.dartlang.org and www.dartlang.org/dart-2.0.)
I also see console warnings in those pages (but 2, not 3). For example, here are the warnings for https://www.dartlang.org/guides/get-started:
I'm using Chrome Canary: Version 64.0.3261.0 (Official Build) canary (64-bit).
The text was updated successfully, but these errors were encountered: