Closed
Bug 881976
Opened 11 years ago
Closed 11 years ago
[webvtt] Implement TextTrackCue::ComputedLinePosition()
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla30
People
(Reporter: reyre, Assigned: reyre)
References
()
Details
(Keywords: dev-doc-needed)
Attachments
(3 files, 4 obsolete files)
9.09 KB,
patch
|
RyanVM
:
checkin+
|
Details | Diff | Splinter Review |
11.10 KB,
patch
|
RyanVM
:
checkin+
|
Details | Diff | Splinter Review |
9.11 KB,
patch
|
rillian
:
review+
RyanVM
:
checkin+
|
Details | Diff | Splinter Review |
TextTrackCue also has a computed line position. The biggest user of this is the processing model. http://dev.w3.org/html5/webvtt/#dfn-text-track-cue-computed-line-position
Comment 1•11 years ago
|
||
It's not clear that it makes sense to stick this in TextTrackCue, but for now I don't have a problem with it really
Assignee | ||
Comment 2•11 years ago
|
||
I'm thinking it should just be a method on the TextTrackCue class. That seems to be what the WEBVTT data model spec is describing.
Blocks: 865407
Assignee | ||
Updated•11 years ago
|
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee | ||
Comment 3•11 years ago
|
||
We won't need to implement this in C++ since we're planning to do the processing model in the JS WebVTT parser. See https://github.com/andreasgal/vtt.js/issues/86 for updates. We should leave this open until the relevant code is landed in the JS parser.
Status: REOPENED → NEW
Comment 4•11 years ago
|
||
Rick, according to https://github.com/mozilla/vtt.js/issues/86, can we mark this as fixed ?
Assignee | ||
Comment 5•11 years ago
|
||
Nope not yet. This is a part of a portion of the processing model that I haven't finished yet (the overlap avoidance part). For some reason I got that link wrong (oops) it should actually be https://github.com/mozilla/vtt.js/issues/103.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rick.eyre
Assignee | ||
Comment 6•11 years ago
|
||
Attachment #8366719 -
Flags: review?(giles)
Attachment #8366719 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 7•11 years ago
|
||
Attachment #8366720 -
Flags: review?(giles)
Attachment #8366720 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 8•11 years ago
|
||
Attachment #8366721 -
Flags: review?(giles)
Assignee | ||
Comment 9•11 years ago
|
||
There's one more patch after this which is currently going through the process of landing in vtt.js. See https://github.com/mozilla/vtt.js/pull/228.
Comment 10•11 years ago
|
||
Comment on attachment 8366719 [details] [diff] [review] Part 1 v1: Expose TextTrack::TextTrackList to Chrome JS r=rillian,bz Review of attachment 8366719 [details] [diff] [review]: ----------------------------------------------------------------- Looks ok to me. Please document _why_ a change is being made in the body of your commit message though. ::: content/media/TextTrack.cpp @@ +205,5 @@ > > +TextTrackList* > +TextTrack::GetTextTrackList() > +{ > + return mTextTrackList.get() ? mTextTrackList : nullptr; Wouldn't an unitialized mTrextTackList already return nullptr here?
Attachment #8366719 -
Flags: review?(giles) → review+
Updated•11 years ago
|
Attachment #8366720 -
Flags: review?(giles) → review+
Comment 11•11 years ago
|
||
Comment on attachment 8366721 [details] [diff] [review] Part 3 v1: Refactor TextTrack classes to store references to eachother in a way that makes more sense. r=rillian Review of attachment 8366721 [details] [diff] [review]: ----------------------------------------------------------------- This is just looking up the parent media element, if any, via the new TextTrackList reference instead of holding a direct reference? I'd shorten the commit title to 'Part 3: Refactor TextTrack class references.' and put the rest in the body.
Attachment #8366721 -
Flags: review?(giles) → review+
Assignee | ||
Comment 12•11 years ago
|
||
(In reply to Ralph Giles (:rillian) from comment #10) > Wouldn't an unitialized mTrextTackList already return nullptr here? Yes, I think so. I was over thinking it with the smart pointer. I'll just return it directly. I can change the other couple places I do this in the patch as well.
Assignee | ||
Comment 13•11 years ago
|
||
(In reply to Ralph Giles (:rillian) from comment #11) > This is just looking up the parent media element, if any, via the new > TextTrackList reference instead of holding a direct reference? Yes. I think it's better to do it this way since a TextTrack will never belong directly to a MediaElement, only through a TextTrackList will it. It also simplifies getting the computed position a little as well. > I'd shorten the commit title to 'Part 3: Refactor TextTrack class references.' and put > the rest in the body. Okay I'll do that. Thanks for review :).
Comment 14•11 years ago
|
||
Comment on attachment 8366719 [details] [diff] [review] Part 1 v1: Expose TextTrack::TextTrackList to Chrome JS r=rillian,bz >+ return mTextTrackList.get() ? mTextTrackList : nullptr; Just: "return mTextTrackList;" r=me
Attachment #8366719 -
Flags: review?(bzbarsky) → review+
Comment 15•11 years ago
|
||
Comment on attachment 8366720 [details] [diff] [review] Part 2 v1: Expose TextTrackList's MediaElement to chrome JS. r=rillian,bz >+ return mMediaElement.get() ? mMediaElement : nullptr; return mMediaElement; r=me
Attachment #8366720 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 16•11 years ago
|
||
Updated commit message and changed TextTrackList getter. Carrying forward r=rillian,bz.
Attachment #8366719 -
Attachment is obsolete: true
Assignee | ||
Comment 17•11 years ago
|
||
Updating commit message and changing HTMLMediaElement getter. Carrying forward r=rillian,bz.
Attachment #8366720 -
Attachment is obsolete: true
Assignee | ||
Comment 18•11 years ago
|
||
Updating commit message. Carrying forward r=rillian.
Attachment #8366721 -
Attachment is obsolete: true
Assignee | ||
Comment 19•11 years ago
|
||
Thanks for review Ralph and Boris. Try push: https://tbpl.mozilla.org/?tree=Try&rev=4086d42b6797
Assignee | ||
Comment 20•11 years ago
|
||
HTMLMediaElement seems to be leaking.
Assignee | ||
Comment 21•11 years ago
|
||
Part 1 of this patch seems to be okay. It's part 2 that introduces the leak. Try push: https://tbpl.mozilla.org/?tree=Try&rev=d82cb8b2dc7f
Assignee | ||
Updated•11 years ago
|
Whiteboard: [leave-open]
Assignee | ||
Updated•11 years ago
|
Attachment #8367305 -
Flags: checkin?
Comment 22•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/183b0963a67b
Flags: in-testsuite+
Updated•11 years ago
|
Attachment #8367305 -
Flags: checkin? → checkin+
Assignee | ||
Comment 23•11 years ago
|
||
I simplified it a bit and made TextTrackList just got to its TextTrackManager for the MediaElement when necessary. This solved the leak as well. Carrying forward r=bz. Try push: https://tbpl.mozilla.org/?tree=Try&rev=31558ba562cc
Attachment #8367307 -
Attachment is obsolete: true
Attachment #8371117 -
Flags: review?(giles)
Updated•11 years ago
|
Attachment #8371117 -
Flags: review?(giles) → review+
Assignee | ||
Updated•11 years ago
|
Attachment #8367308 -
Flags: checkin?
Assignee | ||
Updated•11 years ago
|
Attachment #8371117 -
Flags: checkin?
Comment 26•11 years ago
|
||
Comment on attachment 8371117 [details] [diff] [review] Part 2 v3: Expose TextTrackList's MediaElement to chrome JS. r=rillian,bz https://hg.mozilla.org/integration/mozilla-inbound/rev/a7126bb1c91a
Attachment #8371117 -
Flags: checkin? → checkin+
Comment 27•11 years ago
|
||
Comment on attachment 8367308 [details] [diff] [review] Part 3 v2: Refactor TextTrack classes. r=rillian https://hg.mozilla.org/integration/mozilla-inbound/rev/69bae68bfc68
Attachment #8367308 -
Flags: checkin? → checkin+
Comment 28•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a7126bb1c91a https://hg.mozilla.org/mozilla-central/rev/69bae68bfc68
Status: NEW → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Updated•8 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•