Primary eng (and PM) emails
phi...@opera.comSummary
Motivation
Usage information from UseCounter
Compatibility Risk
Row on feature dashboard?
NoRequesting approval to remove too?
No, wait for data from the stable channel, which is very likely to be in support of removal.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
lgtm
Primary eng (and PM) emails
phi...@opera.comSummary
Deprecate the TextTrackCue constructor, which has been removed from spec.Motivation
When adding VTTCue the TextTrackCue constructor was left for backwards compat pending proof that it could be removed. It has non-trivial custom V8 code to handle the fact that the constructor returns another type than itself, which has caused a memory leak. (That was my fault.)Usage information from UseCounter
The TextTrackCueConstructor use counter was among those listed in <http://crbug.com/332191>. The counter has reached beta.
Compatibility Risk
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
So I guess you should use the VTTCue constructor instead.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
I guess Chrome 33 (approximately less than six weeks from now, or currently in beta, or any latest Chrome 34 canary build) or later?
Though, I do not see three "LGTM"s there (but only two and I have not read the thread again in order to read more verbal "LGTM" statements), the main concern (the specification fork) was resolved since then -So I can only guess Glenn went ahead with the implementation or something.Though this does not matter much (because it would probably be changed accordingly, to match reality), the specification does not state that it is a "[NoInterfaceObject]", so I guess the intention of the implementation is to change the specification.
This works great, until you try to remove the cue. Unfortunately, the removeCue() function only takes at TextTrackCue object as a parameter, so when you try to remove a VVTCue it throws an exception :Failed to execute 'removeCue' on 'TextTrack': parameter 1 is not of type 'TextTrackCue'
On Wednesday, January 15, 2014 at 9:56:56 AM UTC-5, Philip Jägenstedt wrote:Primary eng (and PM) emails
phi...@opera.comSummary
Deprecate the TextTrackCue constructor, which has been removed from spec.Motivation
When adding VTTCue the TextTrackCue constructor was left for backwards compat pending proof that it could be removed. It has non-trivial custom V8 code to handle the fact that the constructor returns another type than itself, which has caused a memory leak. (That was my fault.)Usage information from UseCounter
The TextTrackCueConstructor use counter was among those listed in <http://crbug.com/332191>. The counter has reached beta.Compatibility Risk
Scripts creating TextTrackCues using new TextTrackCue(...) will break. Mostly demos are likely to be affected. It is trivially fixed by using the VTTCue constructor instead.Row on feature dashboard?
NoRequesting approval to remove too?
No, wait for data from the stable channel, which is very likely to be in support of removal.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e0cc3183-eaf3-4686-a503-85ee3c328b0d%40chromium.org.