Changes between Version 8 and Version 9 of Ticket #7338


Ignore:
Timestamp:
03/26/2019 01:24:55 PM (17 months ago)
Author:
kzar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7338 – Description

    v8 v9  
    77Some APIs we use won't be accessible under Service Workers, remove/replace use of those. Specifically:  
    88 
    9 - In `lib/icon.js` we use `Image` to load the icon images, then `document.createElement` to create a `canvas` with their contents as an optimisation (#7253). No plan so far. 
    109- In `lib/subscriptionInit.js` we use `DOMParser` to parse `subscriptions.xml`. We plan to switch to JSON with #7371. 
    1110- In `lib/compat.js` we configure `XMLHttpRequest`, for later use in the core code. We plan to switch to the `fetch` API in the core code with #7381, then we won't need to configure `XMLHttpRequest` any more. 
    1211- In `lib/utils.js` we use `document.addEventListener`, `document.removeEventListener` and `document.readyState` in order to provide `Utils.runAsync` which is used by the core code. Once we stop using `runAsync` with #7406, we can remove this code. 
     12 
     13- In `lib/icon.js` we use `Image` to load the icon images, then `document.createElement` to create a `canvas` with their contents as an optimisation (#7253). No plan so far. 
    1314- In `lib/filterValidation.js` we use `document.createElement`, `document.documentElement.appendChild`, `document.documentElement.removeChild` and `document.querySelector` to create a `style` element which we use to test if a given CSS selector is valid. No plan so far. 
    1415- In `lib/notificationHelper.js` we use `window.confirm` as a fall back for question notifications, where the `Notification` API is faulty/unavailable. No plan so far.