Comment 4 for bug 1586968

I see what’s happening: when OxideQQuickWebViewPrivate::OnEditingCapabilitiesChanged() is initially called, the value of the edit flags stored by the oxide webview is correct (64 == SelectAll), but to retrieve the new value OxideQQuickWebView::editingCapabilities() is called, and at that point (component construction not complete yet), d->proxy_ is null, so NoCapability (0) is returned.

In this light, emitting editingCapabilitiesChanged() in OxideQQuickWebViewPrivate::completeConstruction() after the proxy has been set sounds like a reasonable solution.