216730 2020-09-19 11:15:54 -0700 Remove runtime setting for enabling/disabling GenericCue? 2020-09-26 11:16:12 -0700 1 1 1 Unclassified WebKit Media WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 216512 1 sam webkit-unassigned eric.carlson jer.noble webkit-bug-importer oldest_to_newest 1690095 0 sam 2020-09-19 11:15:54 -0700 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? 1690096 1 sam 2020-09-19 11:16:16 -0700 Jer & Eric, thoughts? 1690321 2 eric.carlson 2020-09-21 09:10:06 -0700 Should we support it in WK1 at all? 1690461 3 sam 2020-09-21 13:03:55 -0700 (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. 1690470 4 eric.carlson 2020-09-21 13:15:19 -0700 (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. 1690580 5 sam 2020-09-21 16:29:49 -0700 (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. 1692200 6 webkit-bug-importer 2020-09-26 11:16:12 -0700 <rdar://problem/69629756>