-
Notifications
You must be signed in to change notification settings - Fork 2
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
[REVIEW, DO NOT MERGE] WebScience Migration Review #96
base: ws-migration-review
Are you sure you want to change the base?
Conversation
Moving page management primarily to the content script environment means we don't need to track window type in the background script environment. Content scripts will only attach in ordinary web content windows.
We haven't had a compelling use case for this functionality, becuase it's generally OK for study logic to ignore pages that are already open when the extension launches. This functionality can also introduce inconsistencies for page measurements.
This functionality is no longer needed, because we can access the page privacy state in the content script environment.
We don't need to store tab information in the background script environment anymore, because we track page information in the content script environment.
We now handle these events in the content script environment.
Replacing tabs.onUpdated with webNavigation.onHistoryStateUpdated to detect History API URL changes, since the former cannot distinguish those changes from ordinary navigation URL changes. This update avoids unnecessary messages to the PageManager content script that can clutter the console.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments from a pass through the updated implementation.
updatedSchema.schema.json
Outdated
"$schema": "http://json-schema.org/draft-04/schema#", | ||
"type": "object", | ||
"mozPipelineMetadata": { | ||
"bq_metadata_format": "pioneer", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rally
?
"newsAndDisinfo.version": { "type": "string" }, | ||
"newsAndDisinfo.pageNavigation": { | ||
"type": "object", | ||
"properties": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Descriptions in here would be helpful.
The `browserConsole` option causes a flood of errors whenever the extension code tries to access the console (e.g. `console.log`), and I couldn't find documentation for it, so I removed it. The appropriate console for the extension still opens.
|
||
"browser_specific_settings": { | ||
"gecko": { | ||
"id": "[email protected]", | ||
"strict_min_version": "60.0" | ||
"id": "[email protected]", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The add-ons team has asked us to change these to end with @rally.mozilla.org
, could we use [email protected]
?
…ageNav presence counts
…udy into ws-migration
No description provided.