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

Jump to bottom

Polymer elements are not evaluated after page reload in dartium (after a certain error has occurred) #20364

Closed
DartBot opened this issue Aug 5, 2014 · 11 comments
Closed

Polymer elements are not evaluated after page reload in dartium (after a certain error has occurred) #20364

DartBot opened this issue Aug 5, 2014 · 11 comments
Labels
P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Aug 5, 2014

This issue was originally filed by felix.ri...@sap.com

What steps will reproduce the problem?

  1. Register onBlur handler on an input field on the page
  2. Remove the input element from DOM with .remove()
       This will cause, which is expected:
       Uncaught NotFoundError: Failed to execute 'removeChild' on 'Node':
       The node to be removed is no longer a child of this node.
       Perhaps it was moved in a 'blur' event handler?
  3. After the exception was thrown hit F5 (or Ctrl + F5 or even Empty cache and hard reload)
  4. Polymer elements are part of the DOM, but screen is blank, the elements are not evaluated. No errors/warning in console.
  5. Open the same URL in a different tab/window works

What is the expected output? What do you see instead?
No matter what kind of errors have occurred, refreshing the page should always work. Dartium seems to cache some state here.

What version of the product are you using?
Dart 1.5.0 - 1.5.8

On what operating system?
Windows 7

What browser (if applicable)?
Dartium Version 36.0.1985.97 (280598)
@kasperl
Copy link

kasperl commented Aug 6, 2014

cc @sigmundch.
Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-High, Area-Pkg, Pkg-Polymer, C7, Triaged labels.

@dgrove
Copy link
Contributor

dgrove commented Aug 20, 2014

Set owner to @jakemac53.

@sigmundch
Copy link
Member

Removed this from the 1.6 milestone.
Added PolymerMilestone-Next label.

@jakemac53
Copy link
Contributor

I wasn't able to get a repro from the description, could you attach an example of this? I was actually not able to reproduce the initial exception, so if you could describe exactly what you were doing there that might help.

Added Waiting label.

@jakemac53
Copy link
Contributor

Added AssumedStale label.

@DartBot
Copy link
Author

DartBot commented Oct 27, 2014

This comment was originally written by felix.ri...@sap.com

I wasn't able to reproduce the exception in a small sample either.
The scenario was the same as described here:
http://stackoverflow.com/questions/21926083/failed-to-execute-removechild-on-node

Maybe the behavior has changed in current Chrome/Dartium, Dart versions.

@jakemac53
Copy link
Contributor

I was able to get a repro on this without using Polymer at all, see https://gist.github.com/jakemac53/f0720f235830065d41a9. This is really just a quirk of chrome it looks like, but working as designed as far as I can tell.

If an input is focused and then removed from the dom, then it fires the blur event after its already been removed (since the blur is a result of it being removed from the dom).

Removed Area-Pkg, Pkg-Polymer, PolymerMilestone-Next labels.
Added AsDesigned label.

@DartBot
Copy link
Author

DartBot commented Oct 28, 2014

This comment was originally written by felix.ri...@sap.com

As described above, the main problem why I raised the issue was not this error, but that after this error has occurred the next page load does not evaluate the polymer elements.
I was able to reproduce it in a small sample:
https://gist.github.com/friegger/ff2c8c2a929be582e7cd

Dart 1.7.2, Polymer 0.15.1+2, Dartium 37.0.2062.120 (292122)

@jakemac53
Copy link
Contributor

Removed Priority-High label.
Added Priority-Medium, Pkg-Polymer, Area-Pkg, Accepted labels.

@jakemac53
Copy link
Contributor

Thanks for the repro, I can confirm its happening to me as well. This looks like a dartium bug, so it should only affect you during development. Once compiled to javascript I am not seeing this issue (tested chrome and firefox).

Removed Pkg-Polymer, Area-Pkg labels.
Added Area-Dartium, Triaged labels.

@jakemac53
Copy link
Contributor

Removed the owner.

@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@kevmoo @matanlurey @jakemac53 @sigmundch @dgrove @kasperl @DartBot