new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Electron · API · all subjects

webcontents/navigation

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Event: will-navigate fires only for main frame navigation

The will-navigate event only fires when the mainFrame navigates. If you want to also observe navigations in iframes, use will-frame-navigate and did-frame-navigate events instead.

Document navigation events fire in order

When a webContents navigates to another page (as opposed to in-page navigation), the following events will be fired in this order: did-start-navigation, will-frame-navigate, will-navigate (only for main frame), will-redirect (only if redirect happens), did-redirect-navigation (only if redirect happens), did-frame-navigate, did-navigate (only for main frame). Subsequent events will not fire if event.preventDefault() is called on any of the cancellable events.

In-page navigation events

In-page navigations don't cause the page to reload but instead navigate to a location within the current page. These events are not cancellable. For in-page navigations, the following events will fire in this order: did-start-navigation, did-navigate-in-page.

Give your agent this brain