TEST Check that PageTransition keeps bf flag

content/browser/frame_host/navigation_handle_impl.cc

Index: content/browser/frame_host/navigation_handle_impl.cc
diff --git a/content/browser/frame_host/navigation_handle_impl.cc b/content/browser/frame_host/navigation_handle_impl.cc
index af783af8f957c69c64180d685d385792af26f32a..86034afa17b9322de3268ff4e81129da8e159110 100644
--- a/content/browser/frame_host/navigation_handle_impl.cc
+++ b/content/browser/frame_host/navigation_handle_impl.cc
@@ -743,6 +743,9 @@ void NavigationHandleImpl::DidCommitNavigation(
   DCHECK_EQ(frame_tree_node_, render_frame_host->frame_tree_node());
   CHECK_EQ(url_, params.url);
 
+  CHECK_EQ(transition_ & ui::PAGE_TRANSITION_FORWARD_BACK,
+           params.transition & ui::PAGE_TRANSITION_FORWARD_BACK);

[nasko, 2017/06/23 13:40:38]

One of the cases where this is hit is for history navigation to a NavEntry
result from pushState. The handle starts with empty page transition, we don't
have a network request to update it, then at commit time we get a back/forward
transition, which doesn't match the empty transition.

+
   did_replace_entry_ = did_replace_entry;
   method_ = params.method;
   has_user_gesture_ = (params.gesture == NavigationGestureUser);