Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop line: and position: settings with invalid linealign/colalign #337

Merged
merged 1 commit into from
Mar 27, 2017

Conversation

zcorpan
Copy link
Member

@zcorpan zcorpan commented Mar 3, 2017

Fixes #336.

index.bs Outdated
substring of |value| up to and excluding the first U+002C COMMA character (,) in that string
and let |linealign| be the trailing substring of |value| starting from the character
immediately after the first U+002C COMMA character (,) in that string.</p></li>
<li><p>If |value| contains a U+002C COMMA character (,) that is not the last character in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason behind making this more complicated? The substring after the , when its at the end should be empty anyway, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted line:50, to be dropped. But maybe can set linealign to null instead of empty string, and check for that, instead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want the comma version to take priority over the non comma version, we should allow this as one where the parameters take the default value, I.e. linealign=start, seeing as if we make this extensible with further parameters, we will not always expect all the parameters to be present.
E.g. line:50,XYZ=blah should still take precedent over line:50 and result in linealign getting the default value.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. ^_^ This is ugly as it is, let's not consider making it worse. But even so, XYZ is invalid now and should still cause the whole thing to be dropped.

@BenjaminSchaaf
Copy link
Contributor

LGTM otherwise.

Other than the step 1 changes, I've already changed the parser in wpt to match, pending changes to other tests.

@zcorpan
Copy link
Member Author

zcorpan commented Mar 6, 2017

Fixed step 1, PTAL

@silviapfeiffer
Copy link
Member

WFM

@zcorpan
Copy link
Member Author

zcorpan commented Mar 10, 2017

@BenjaminSchaaf

Other than the step 1 changes, I've already changed the parser in wpt to match, pending changes to other tests.

Could you upload this as a PR to web-platform-tests, even if incomplete?

BenjaminSchaaf added a commit to BenjaminSchaaf/web-platform-tests that referenced this pull request Mar 10, 2017
@BenjaminSchaaf
Copy link
Contributor

Created here: web-platform-tests/wpt#5113

@zcorpan
Copy link
Member Author

zcorpan commented Mar 10, 2017

zcorpan pushed a commit to BenjaminSchaaf/web-platform-tests that referenced this pull request Mar 21, 2017
zcorpan pushed a commit to web-platform-tests/wpt that referenced this pull request Mar 27, 2017
Update parser for w3c/webvtt#337

Update parser to drop `line:1,` and update tests
@zcorpan zcorpan force-pushed the zcorpan/drop-invalid-linealign branch 2 times, most recently from d9a2a9f to f1ea632 Compare March 27, 2017 08:54
@zcorpan zcorpan merged commit 76e97e7 into gh-pages Mar 27, 2017
@zcorpan zcorpan deleted the zcorpan/drop-invalid-linealign branch March 27, 2017 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants