| Summary: | Remove runtime setting for enabling/disabling GenericCue? | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Weinig <sam> |
| Component: | Media | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | eric.carlson, jer.noble, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 216512 | ||
|
Description
Sam Weinig
2020-09-19 11:15:54 PDT
Jer & Eric, thoughts? Should we support it in WK1 at all? (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. (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. (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. |