Remove inaccurate bulletpoint on Firefox-Safari incompatibility (#18268)

files/en-us/web/api/storage_access_api/index.md

@@ -53,7 +53,6 @@ When `requestStorageAccess()` is called by an embedded, cross-origin document, t
 Although the API surface is the same, websites using the Storage Access API should expect differences in the level and extent of storage access they receive between Firefox and Safari. This is caused by differences in the storage access policies implemented in the two browsers. Design properties unique to Firefox are summarized here:
 
 - If the embedded origin `tracker.example` has already obtained first-party storage access on the top-level origin `foo.example`, and the user visits a page from `foo.example` embedding a page from `tracker.example` again in less than 30 days, the embedded origin will have storage access immediately when loading.
-- If a page from top-level origin `foo.example` embeds more than one {{htmlelement("iframe")}} from `tracker.example`, and one of those `<iframe>`s uses the Storage Access API in order to obtain storage access successfully, all other iframes from `tracker.example` on `foo.example` top-level origins will immediately gain storage access as well, without needing to call `requestStorageAccess()` separately.
 - If an embedded page from `tracker.example` has previously successfully obtained storage access on top-level origin `foo.example`, all embedded subresources from `tracker.example` on `foo.example` (e.g. scripts, images, stylesheets, etc.) will load with access to their first-party storage, which means they may send Cookie headers and honor incoming {{httpheader("Set-Cookie")}} headers.
 - In Firefox, when the promise returned from `requestStorageAccess()` is resolved, the embedded page will gain access to its entire first-party storage, not just cookies.  This includes access to APIs such as [Web Storage](/en-US/docs/Web/API/Web_Storage_API), [IndexedDB](/en-US/docs/Web/API/IndexedDB_API), [DOM Cache](/en-US/docs/Web/API/Cache), and so on.
 - In Firefox, the storage access grants are phased out after 30 calendar days passing, whereas in Safari the storage access grants are phased out after 30 days of browser usage passed without user interaction. This is currently a limitation of the Firefox implementation, which we may address in a future version.  In Safari, successful use of the storage access API resets this counter.