Geek Answers Handbook

Responsive design and viewport do not work through a domain set of frames.

I am working on a responsive design site and have run into a pretty big problem. I used the viewport code:

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0" />

and used:

 @media only screen and (min-width: 501px) and (max-width: 930px) {

CSS HERE}

as needed. When I put my index page on my host server to check that the site will not respond to changes between my mobile devices. I tried my domain site - it didn’t work. It turns out that the domain name points to my segment and displays the site in a <frameset> and cancels my CSS and meta. When I go to the server’s own web address, it works correctly. Anyway, around?

+4
source share
3 answers

I installed a responsive design site that uses the client’s browser window to determine how the site is configured. It turned out that my domain name was redirected using masking, and CSS "read" the frame as a viewport. disaster prevention.

-1
source

SOLVED - I found a solution using the well-known hacking technology to enter the appropriate code (without actually hacking anything!).

I have a domain name on 123-reg.co.uk and free web space on freehostingEU, with a web forwarding frame on 123-reg.co.uk to maintain my domain name in free space. To solve the problem of blocking the metadata meta tag on the site, go to website redirection settings somewhere like 123-reg.co.uk, where you can usually specify your meta title, meta script, meta author, etc. And enter the following code into one of the fields where you are allowed to enter some metadata for your page with a frame, for example, a meta-author and insert: -

  your-author-name"><meta name="viewport" content="width=device-width, initial-scale=1.0,

which will then place the viewport code on the frame redirect page immediately after the meta-author. And it works because I just did it on 123-reg and it works great!

+6
source

This site finally explained how I can do this with me. Now, when you visit mydomain.com, it goes to the site www.mydomain.com, which, in turn, connects to my azure server. The domain remains in the URL without frames / masking, i.e. shows the URL that I bought, not azure.

http://blog.smarx.com/posts/custom-domain-names-in-windows-azure

From the link:

Add CNAME Record

Step one is to create a CNAME record that displays the www subdomain (as on www.botomatic.com) for my Windows Azure application (botomatic.cloudapp.net)

Forward root domain

Step two is to use domain forwarding to map the root domain (botomatic.com) to a subdomain that we have already mapped (www.botomatic.com).

+1
source

More articles:


All Articles