Add width/height settings per context

Same problem. Here a quick patch adding width / height per context settings. I'm not sure this is the right way to do this but it's working for me.

It was discussed briefly in the past but has not been decided. The idea is to have a width/height setting in each context. It usually makes sense, unless it comes to responsive design. But in the latter case, it can use "auto" dimensions.

If you think it is good, then let's implement it. We needs width/height setting (beside transcoder, player) in each context and providers would use that to render.

If it is a context setting, it will automatically exportable.

I have run in to the same issue but with another third video provider integration I am working on. To implement a "provider_scald_player" works, but breaks the scald abstraction that all videos are just "videos". If you were to use a vimeo video in a youtube player that would not work, so as soon as you need to set height, with, autoplay and other settings for a context you basically lock in to one provider. How would the "scald" way of solving this be?

(On way would I guess be to have a generic player, with settings that all video providers should be able to implement, but that would restrict all settings to the least common denominator, and generally be a pretty non elegant solution.)

It does work, but I wonder about the implementation as @gnucifer does. I suppose you could create a separate context for youtube v. other videos and switch it out in ckeditor with a right-click. If there were an official implementation of this in the module in the near future, that would be awesome. Thanks again for an awesome module and looking forward to implementing on our big project! Thanks for the support.

To take the concern a bit further, it's going to be confusing to our content editors to select, say "Full Width" context and they're trying to render an uploaded video from the server, not youtube, so I guess the way around this for now is to either a) separate out youtube as a different atom type with its own set of contexts or b) add contexts that are specific for youtube and default sensible as well as name the contexts where it will be easy for our non-technical content-editors to handle this. I'm leaning towards option a at the moment.

I concidered a) when implementing my new atom provider (a video service) but in the end went with the "video" type which enabled the customer to mix youtube/vimeo and "myprovider" in the same field. This was much appreciated and in hindsight any other approach would have been wrong (at least customer satisfaction-wise). I'm leaning more towards trying to establish some generic interface for all video providers, and video provider may choose to implement none, some or all of the provided settings. This is not ideal though, but the best I can think of without introducing a heckload of additional abstractions.

Promoting priority because with #2188415: Youtube provider does not import tags and recognizes correctly video dimensions getting in, lots of YouTube videos will have large dimensions that are not usable by default.

I'm working on this.

Change notice added https://www.drupal.org/node/2340821.

It seems this neglected to add support for exporting these settings via Features?

Furthermore: the problem seems to be that these dimensions are per-context rather than per-bundle-per-context like the other context settings that get stored in Features. Is there a reason this was done this way?

I've opened #2600088: Context dimensions aren't per-bundle

Adding Features support for this here: #2600130: 'data' attributes of context configuration (such as dimensions) don't get exported to Features