Bug 249266
| Summary: | Figure out how to tell if a Web Extension has been updated in WebKit | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kiara Rose <kiara_rose> |
| Component: | WebKit Extensions | Assignee: | Timothy Hatcher <timothy> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Kiara Rose
Figure out how to tell if a Web Extension has been updated in WebKit and remove the background page listeners if the extension has been updated.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kiara Rose
When developers are making local changes to their extension for testing, they're likely not changing the extension version number.
Kiara Rose
One option would be the take a hash of all the files in the bundle, and if any change assume it changed
Radar WebKit Bug Importer
<rdar://problem/103573769>
Timothy Hatcher
One option is to check and remember the previous code signing hash. That should change everything there is a change in the bundle.
Kiara Rose
Tim mentioned an idea of hashing all the files and seeing if the hash changes
Timothy Hatcher
Pull request: https://github.com/WebKit/WebKit/pull/26778
EWS
Committed 277022@main (adf9728dc4e1): <https://commits.webkit.org/277022@main>
Reviewed commits have been landed. Closing PR #26778 and removing active labels.