NEW 216730
Remove runtime setting for enabling/disabling GenericCue? 
https://bugs.webkit.org/show_bug.cgi?id=216730
Summary Remove runtime setting for enabling/disabling GenericCue?
Sam Weinig
Reported 2020-09-19 11:15:54 PDT
The GenericCueAPIEnabled experimental preference is currently enabled by default in WebKit2, but disabled by default in WebKitLegacy. Can we enabled generic cue in WebKitLegacy? If not, can we at least remove the experimental setting in WebKit2 now?
Attachments
Add attachment proposed patch, testcase, etc.
Sam Weinig
Comment 1 2020-09-19 11:16:16 PDT
Jer & Eric, thoughts?
Eric Carlson
Comment 2 2020-09-21 09:10:06 PDT
Should we support it in WK1 at all?
Sam Weinig
Comment 3 2020-09-21 13:03:55 PDT
(In reply to Eric Carlson from comment #2) > Should we support it in WK1 at all? If we can without undue burden, I think it makes things more straightforward to support them universally.
Eric Carlson
Comment 4 2020-09-21 13:15:19 PDT
(In reply to Sam Weinig from comment #3) > If we can without undue burden, I think it makes things more straightforward > to support them universally. It isn't a burden, but it seems strange to add new features to something we don't want people to use.
Sam Weinig
Comment 5 2020-09-21 16:29:49 PDT
(In reply to Eric Carlson from comment #4) > (In reply to Sam Weinig from comment #3) > > If we can without undue burden, I think it makes things more straightforward > > to support them universally. > > It isn't a burden, but it seems strange to add new features to something we > don't want people to use. Most features we add aren't behind a feature flat at all, so we do this all time implicitly. If we want to stop making features available to WebKit1, we will really need to fork it off.
Radar WebKit Bug Importer
Comment 6 2020-09-26 11:16:12 PDT
<rdar://problem/69629756>
Note You need to log in before you can comment on or make changes to this bug.