https://angular.io/guide/reactive-forms shows empty page #24973

Activity

1. manklu commented on Jul 18, 2018

   

   manklu

   on Jul 18, 2018

   More actions

   Works for me without problems. Which browser did you use?
2. ukrukarg commented on Jul 18, 2018

   

   ukrukarg

   on Jul 18, 2018

   Author

   More actions

   Actually, now it also works for me. Guess all I had to do was complain :)

   😄React with 😄1Reacted by manklu
3. ukrukarg

   closed this as completedon Jul 18, 2018
4. krcourville commented on Aug 18, 2018

   

   krcourville

   on Aug 18, 2018

   Last edited by krcourville

   More actions

   Little more background on this...

   I'm seeing this issue on several documentation pages using Chrome 68 on Mac. Safari seems to work ok.

   Some pages I've run across so far that exhibit this behavior:

   • https://angular.io/guide/bootstrapping
   • https://angular.io/guide/frequent-ngmodules
   • https://angular.io/guide/singleton-services

   The error in the console is:

   ERROR [DocViewer] Error preparing document 'guide/singleton-services': Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
       at t.extractHeadingSafeHtml (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:264514)
       at https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:263980
       at Array.map (<anonymous>)
       at t.genToc (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:263947)
       at https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:307681
       at e._next (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:309978)
       at e.__tryOrSetError (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:52231)
       at e.next (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:51342)
       at e._next (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:50476)
       at e.next (https://angular.io/main.2ce174b314884f005f8b.bundle.js:1:50147)
   

   But then, I did an Empty Cache and Hard Reload, and all is well.
5. gkalpak commented on Aug 20, 2018

   

   gkalpak

   on Aug 20, 2018

   Member

   More actions

   Thx for the extra info, @krcourville. Interestingly, though, extractHeadingSafeHtml() does not contain any call to removeChild() 😕
   (Sounds like a Chrome bug.)
6. yongzhi-chen commented on Sep 19, 2018

   

   yongzhi-chen

   on Sep 19, 2018

   Last edited by yongzhi-chen

   More actions

   @gkalpak from the chrome inspector the function extractHeadingSafeHtml clearly has removeChild function. I guess the bundle js is not using the latest version?

   t.prototype.extractHeadingSafeHtml = function(t) {
                   var e = this.document.createElement("a");
                   e.innerHTML = t.innerHTML;
                   var n = e.querySelector("a");
                   return n && e.removeChild(n),
                   this.domSanitizer.bypassSecurityTrustHtml(e.innerHTML.trim())
               }
   
7. gkalpak commented on Sep 19, 2018

   

   gkalpak

   on Sep 19, 2018

   Member

   More actions

   This code is from before 12be311. The current version uses different code.
   How come you are getting that old version? I wonder if the SW was keeping you back to an old version.
   (Fortunately, we are switching to the latest SW which should be more reliable: #25997)
8. yongzhi-chen commented on Sep 19, 2018

   

   yongzhi-chen

   on Sep 19, 2018

   More actions

   hmm it does seem like it. the service worker caches the entry html so Chrome was using the old main.js
9. angular-automatic-lock-bot commented on Sep 14, 2019

   

   angular-automatic-lock-botBot

   on Sep 14, 2019

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
10. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Sep 14, 2019