mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-10 00:12:09 +00:00
New note: Targeting secure browser profiles
This commit is contained in:
parent
5cdabcde40
commit
5637aca18c
1 changed files with 8 additions and 0 deletions
8
content/notes/targeting-secure-browser-profiles.md
Normal file
8
content/notes/targeting-secure-browser-profiles.md
Normal file
|
@ -0,0 +1,8 @@
|
||||||
|
---
|
||||||
|
title: "Targeting secure browser profiles"
|
||||||
|
date: 2023-08-28T19:10:31-07:00
|
||||||
|
---
|
||||||
|
It's hard to target browsers' secure profiles. Safari's Lockdown Mode disables a dozen or so APIs and a handful of other features; the Tor Browser disables another handful of features; Microsoft Edge will likely land more changes to Enhanced Security mode in the coming years. Barely any of this is documented.
|
||||||
|
|
||||||
|
[I filed a bug in MDN's BCD tracker](https://github.com/mdn/browser-compat-data/issues/20619) to fill this gap, listing what I knew. We can't expect developers to navigate the dozens of WebKit blog posts and Tor Browser JSM files to figure out which features are disabled. Of course, progressive enhancement should be the norm, but it's helpful to have a real baseline.
|
||||||
|
|
Loading…
Reference in a new issue