Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are declaring the width and height in the html element: </p> <pre><code> &lt;video id="sms1_video"class="video-js vjs-default-skin" controls preload="auto" width="900" height="600" poster="images/sms/AnimationScreen_SMSXMAS.jpg" data-setup="{}"&gt; </code></pre> <p>Regardless of what you put in the CSS the video will stay 900 x 600. </p> <p><strong>Instead:</strong> Change that to width=100% and remove the height component. Then you can put a wrapper on the video and size that in the CSS. </p> <p>See this helpful tutorial for the full explanation: </p> <p><a href="http://www.netmagazine.com/tutorials/create-fluid-width-videos" rel="nofollow">http://www.netmagazine.com/tutorials/create-fluid-width-videos</a></p> <p><strong>EDIT:</strong> Your site has this code: </p> <pre><code>&lt;div class="videowrapper"&gt;&lt;video id="sms1_video" class="video-js vjs-default-skin" controls="" preload="auto" width="100%" poster="images/sms/AnimationScreen_SMSXMAS.jpg" data-setup="{}"&gt; &lt;source src="images/interactive/SMS_2011ChristmasAnimation.mp4" type="video/mp4"&gt;&lt;!-- MPEG4 for Safari --&gt; &lt;source src="images/interactive/SMS_2011ChristmasAnimation.ogv" type="video/ogg"&gt; &lt;!-- Ogg Theora for Firefox 3.1b2 --&gt; &lt;source src="images/interactive/SMS_2011ChristmasAnimation.webm" type="video/webm"&gt; &lt;/video&gt; &lt;/div&gt; </code></pre> <p>the <code>&lt;div class="videowrapper"&gt;</code> needs some width or height in the css. You can set this with media queries to resize based on the browser size.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload