An invaluable addition to @ChromeDevTools would be an ability to pause at the code which attempts to navigate or reload (most important via `location.href` which cannot, to my knowledge, be captured by monkey-patching). Currently it only can pause on an unload event *handler*.
-
-
Replying to @sompylasar
My hunch is that this is solvable via the Console. I'll dig into it and get back to you. --- kayce
1 reply 0 retweets 3 likes -
Replying to @ChromeDevTools @sompylasar
Addy suggested an Object.observe() polyfill, using ES6 proxies. I'm going to explore that route. --- kaycehttps://gist.github.com/ebidel/1b553d571f924da2da06 …
1 reply 0 retweets 0 likes -
Replying to @ChromeDevTools @sompylasar
Well, I tinkered around and couldn't get anything working. So I think you're right, there's no way to monkey patch this... forwarding feedback to the team... --- kayce
1 reply 0 retweets 1 like -
Replying to @ChromeDevTools @sompylasar
Actually, @somplylasar, what about just searching for location.href in the global Search tab, and then manually adding a breakpoint on each call?pic.twitter.com/AzXc9EnX7R
1 reply 0 retweets 1 like -
Replying to @ChromeDevTools
1) Breakpoints set manually aren't working reliably, too, especially on a minified codebase, I wrote about it a while ago. 2) Not every piece of code that gets executed may show up at the time of navigation. For me, the code was reloading itself on page load.
1 reply 0 retweets 0 likes -
Replying to @sompylasar
Have you filed a bug on #1? If you've got a repro URL, that'd be helpful (you can privately submit it to us)
1 reply 0 retweets 0 likes -
Replying to @ChromeDevTools
No, I haven't. I'm really sorry I don't currently have time to isolate the bug and formulate a bug report for you. It's not reliably reproducible and I learned to deal with it; when it happens, there's usually more important things to do (i.e. debug the app, not the devtools).
1 reply 0 retweets 0 likes
OK, sorry to hear about the troubles. If you want to share your tech stack, that may help us reduce variables
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.