-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native re-implementation of Web Discovery (part 1) #39439
Native re-implementation of Web Discovery (part 1) #39439
Comments
@DJAndries is this ready for QA? If so, can you please add a test plan? Thanks! |
Hey @LaurenWags , we are still waiting for the Android scraping rules to be published. Once that is complete (hopefully over the next couple of days), I will add a test plan, thank you. cc @remusao |
@DJAndries can we get an update on this please? Thanks. |
The Search team are still in the process of updating their scraping patterns, but they confirmed that they should have it wrapped up by the end of the week. I hope to have a test plan ready tomorrow or early next week. |
Here is a test plan, please hold until brave/brave-core#27788 is merged and uplifted:
At some point, a "preparing" log with the Query payload:
|
Thanks @DJAndries - looks like this test plan is Android specific though. What should be checked for desktop since this issue has cc @kjozwiak |
We won't be using the native implementation on Desktop just yet. I went ahead and removed the |
So brave/brave-core#27788 was merged into |
QA is blocked until brave/brave-core#27814 is merged |
@Uni-verse @hffvld unblocked as the above was merged/uplifted into |
Verified on
STEPS:
ACTUAL RESULTS:
Galaxy Tab S8Pixel 7 |
Currently, the Web Discovery Project exists as part of the embedded Brave extension. In order for Android/iOS users to opt-in and participate in Web Discovery, the client must be re-implemented natively.
Web Discovery sends three types of payloads:
alive
: a ping to indicate to the Web Discovery servers that the user is opted inquery
: search engine results, if the query is deemed to not contain private informationpage
: page interaction events, to measure user engagement for non-private pagesThe initial re-implementation will only cover the first two payloads. The third payload will be covered in a separate issue. In addition, a separate issue will be needed for iOS in order to cover some WebKit renderer necessities.
A feature controlled by variations (
BraveWebDiscoveryNative
) will be used to handle the rollout to mobile users. Once thepage
payload is implemented, we can begin to deprecate the extension code by rolling the feature out to desktop users.cc @anthonypkeane @rebron @bbondy @aekeus @remusao
The text was updated successfully, but these errors were encountered: