I’m not sure where the root cause of the issue lies (cc::CompositorFrameMetadata::top_controls_height and cc::CompositorFrameMetadata::top_controls_shown_ratio having non-number values), this would require further investigation to determine. The following patch works around the issue:
Note that the code for the location bar controller has been significantly reworked in oxide since then, so it’s hard to tell whether the issue (which doesn’t exhibit in master) has been fixed in oxide itself or whether it was a bug in chromium that has been fixed since then.
WebView: :GetLocationBar ContentOffset( ) returns -nan.
I’m not sure where the root cause of the issue lies (cc::Compositor FrameMetadata: :top_controls_ height and cc::CompositorF rameMetadata: :top_controls_ shown_ratio having non-number values), this would require further investigation to determine. The following patch works around the issue:
float WebView: :GetLocationBar ContentOffset( ) const { frame_metadata( ).top_controls_ height *
compositor _frame_ metadata( ).top_controls_ shown_ratio; offset) ) {
float offset = compositor_
if (std::isnan(
return 0.f;
}
return offset;
}
Note that the code for the location bar controller has been significantly reworked in oxide since then, so it’s hard to tell whether the issue (which doesn’t exhibit in master) has been fixed in oxide itself or whether it was a bug in chromium that has been fixed since then.