Thank you for adding this. Finally we're going to be able to do
cross-browser video-recordings and playing. Can't wait to see it in
production.
M.
On Monday, March 4, 2024 at 3:50:13 PM UTC-7 sun...@microsoft.com wrote:
> Mike, I've added feature detection and developer engagement on
>
Thanks @Chris Palmer for your input. Nobody is more opposed to DRM than I
am. Even today I refuse to load DRM extensions into the browser. I think
that DRM is wrong and the open web is the way to go.
But providing provenance and integrity to a resource is not DRM. TLS is not
DRM. If you hit a
There are a number of things to consider:
*It's my device, and I have the right to do what I want to do with it. Not
somebody else.*
While I am 100& supporting this statement, this ship has sailed a long time
ago. Our friends @Google already control many things that especially
influence the life
It would be my suggestion that a "broken" integrity should result in a
browser warning (like an invalid TSL certificate) allowing the user to
continue if he/she so chooses. That would allow "twiddling" while also
giving a normal user an amount of security that nobody else has "twiddled"
with the
Thank you Francois. Here's an experience I'd like to share with you. I was
watching and listening to a training presentation yesterday and was asked
to look something up. So I opened a new tab to start looking it up. But the
presentation in the first tab stopped and I was unable to use the second
We are categorically against this. It severely limits developers to what is
considered to be "good practice" which is not always desired (or possible),
especially not in complex environments. We are frankly getting tired to be
told what is "good" and what is "bad" behavior without any
Ben: I must have read the explainer incorrectly. Yes I am proposing a an
integrity check for user agents to run against websites.
Here are my thoughts:
Web-environments are used to transport and process critical data. In order
to protect the integrity of the web-environment, we have mechanisms
I am a *big* fan pf everything that helps to protect the integrity of a
web/javascript environment. Not necessarily to make a site or web/app
unusable, but to inform the user that an evironment has changed. It is up
to the user to decide to continue to use it or not. To that end I am
proposing
Thanks for your answer Rick. However - I do have some remarks. An
incoming call notification should reliably and across all platforms signal
a .. well, incoming call. What good is a notification if it works on some
platforms and doesn't work for others. Take webPush for example: It is
pretty much
I strongly support this API. There's always the potential for misuse, all
the user has to do is to uninstall the app. I understand the principle
philosophy to protect the user against malicious intends, but this should
never lead to overly restrictive functionality. WebApps .. as they are
10 matches
Mail list logo
