|
|
|
|
|
by aghull
4858 days ago
|
|
This is the same behaviour as Safari has had by default for years. App developers that depend on 3rd-party cookies should in general already have the work-arounds in place to support Firefox 22 assuming they already support Safari. |
|