Re: [webkit-dev] Request for position: EME MediaKeySession Closed Reason

2021-06-15 Thread 王消寒
+Jer Kindly ping! Thanks! On Tue, Jun 8, 2021 at 11:36 AM Xiaohan Wang (王消寒) wrote: > This is a request for WebKit's position on the "EME MediaKeySession Closed > Reason" proposal: > > *Links* > >- W3C EME spec issue/explainer: >https://github.com/w3c/encrypted-media/issues/473 >-

Re: [webkit-dev] Removing the ENABLE(CSS_SCROLL_SNAP) flag

2021-06-15 Thread Simon Fraser via webkit-dev
Sounds fine. Simon > On Jun 15, 2021, at 5:04 AM, Martin Robinson via webkit-dev > wrote: > > Recently, css-scroll-snap was enabled on all ports. The implementation > has also been extended to be mostly platform-independent. Since all > ports are compiling this code and it's a fairly basic CSS

Re: [webkit-dev] Removing the ENABLE(CSS_SCROLL_SNAP) flag

2021-06-15 Thread Michael Catanzaro via webkit-dev
Hi Martin! My $0.02: when all ports have the feature enabled and the code is cross-platform, it's usually best to remove the build flag unless there's a particular strong reason to keep it around. We have more than enough build flags, and if you get to delete old code that just makes it eve

Re: [webkit-dev] Request for position: preferCurrentTab

2021-06-15 Thread Elad Alon via webkit-dev
> > Doesn't this property go against that conscious design decision? What is > your security analysis here? Both preferCurrentTab=true as well as preferCurrentTab=false result in a user-prompt that is spec-compliant. (The user agent is free to display the current tab as the most prominent option

[webkit-dev] Removing the ENABLE(CSS_SCROLL_SNAP) flag

2021-06-15 Thread Martin Robinson via webkit-dev
Recently, css-scroll-snap was enabled on all ports. The implementation has also been extended to be mostly platform-independent. Since all ports are compiling this code and it's a fairly basic CSS feature should we go ahead and remove the ENABLE(CSS_SCROLL_SNAP) build flag? I think this would grea