Note that there are some explanatory texts on larger screens.

plurals
  1. POCSS Media Queries working in Dolphin browser but not Chrome or Safari?
    primarykey
    data
    text
    <p>I've done a lot of reading off of stackoverflow and various sites off of google, but I haven't been able to find a solution for this yet. :(</p> <p>I have in my header:</p> <pre><code>&lt;meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=1" /&gt; ... &lt;link rel="stylesheet" href="&lt;?php echo get_template_directory_uri(); ?&gt;/mobile-style.css" /&gt; </code></pre> <p>(I originally only had the first two in my meta viewport content (width=device-width, initial-scale=1.0), but added the second two after reading through some articles.)</p> <p>In my <code>mobile-style.css</code> file, I have:</p> <pre><code>@media only screen and (max-device-width: 568px;) { ... } </code></pre> <p>I have experimented with the max-device-width here as well, it has been 320, 480, 600, and 680... none of them work.</p> <p>I can view this mobile stylesheet on my xperia Z using the dolphin browser (but not the Chrome browser), and on my friend's iPhone 3GS. Elsewhere it doesn't show up. The goal is just a simple mobile layout for the current site for any smaller-sized screen device.</p> <p>Let me know if I should be providing more information. </p> <p>Thanks! :)</p> <p><strong>EDIT</strong></p> <p>Here is the gist for my mobile-style.css file: <a href="https://gist.github.com/melissanoelle/7043032" rel="nofollow">https://gist.github.com/melissanoelle/7043032</a></p> <p>Sorry for the delay, I've been away from a computer while traveling for my grandfather's funeral. :(</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. This table or related slice is empty.
    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