Let getSettings() return the constrained track resolution, not source.

content/renderer/media/media_stream_video_track.h

Index: content/renderer/media/media_stream_video_track.h
diff --git a/content/renderer/media/media_stream_video_track.h b/content/renderer/media/media_stream_video_track.h
index 364a64e73525ae6006a88c478576982ed0a153c5..72ead10c4432aff5810f0db957e27d65d73cc425 100644
--- a/content/renderer/media/media_stream_video_track.h
+++ b/content/renderer/media/media_stream_video_track.h
@@ -61,6 +61,13 @@ class CONTENT_EXPORT MediaStreamVideoTrack : public MediaStreamTrack {
 
   const blink::WebMediaConstraints& constraints() const { return constraints_; }
 
+  // Setting information about the track size.
+  // Called from MediaStreamVideoSource at track initialization.
+  void SetTargetSize(int width, int height) {

[Guido Urdaneta, 2017/03/13 14:12:37]

Is there a reason why the track cannot set these values itself during
initialization?

[hta - Chromium, 2017/03/13 15:04:35]

Yes - when it is created, I don't think the resolution is decided yet, and after
creation, it can't easily navigate the hierarchy of objects involved.

It is better for the track to be told by upstream what the resolution is than to
have the track ask the upstream about it.

The way it is set, these variables are empty if not set.
I also wanted to have the opportunty to change them if something changes
upstream (such as calling applyConstraints) - which requires a function anyway.

+    width_ = width;
+    height_ = height;
+  }
+
  private:
   // MediaStreamVideoSink is a friend to allow it to call AddSink() and
   // RemoveSink().
@@ -95,6 +102,10 @@ class CONTENT_EXPORT MediaStreamVideoTrack : public MediaStreamTrack {
   // This is used for tracking if all connected video sinks are secure.
   SecureDisplayLinkTracker<MediaStreamVideoSink> secure_tracker_;
 
+  // Remembering our desired video size.
+  int width_ = 0;
+  int height_ = 0;
+
   DISALLOW_COPY_AND_ASSIGN(MediaStreamVideoTrack);
 };