Steps to reproduce:
Background setup:
- use a non-private tab (to ensure cookies are being retained)
- don't use any paywall bypass plugins that might interfere with cookies (although in my testing I am not sure they're able to control cookies yet, which may be a separate bug)
- using a website that makes use of a soft paywall via cookies is the easiest way to demonstrate this issue, though the bug is about the functionality of the menu item
Reproduction steps:
- In a non-private window, browse to a paywalled article (example - https://www.ft.com/content/2a96995b-c799-4281-8b60-b235e84aefe4)
- In the same window, attempt to browse to a second article (example - https://www.ft.com/content/8fd0bb2b-429d-4699-a6d4-aac20e01641f)
- You should see a paywall rather than the second article. This is due to cookies being set.
- Open Develop > Edit Cookies in the FT.com tab so you can look at the cookies. Note the cookies that are set and their values. As a specific example, note the value of cookie named "FTAllocation".
- Use Develop > Empty Cookies and Storage for ft.com
- Refresh the page, and notice that all the same cookies are in place. Attempt to visit the second article above, and note it is still paywalled.
- Counter-factual to demonstrate clearing cookies manually works - right-click and delete the "FTAllocation" cookie manually
- Visit the second article above, and notice you can access it.
Expected behavior:
When the Develop > Empty Storage and Cookies for <site.tld> menu item is used, it should clear all cookies set on the domain, as well as local storage, session storage and indexed storage.
Orion, OS version; hardware type:
Version 0.99.123.3.5-rc (WebKit 616.1.4.5)