I think we have just about beat this subject to death. But, I still have a hard time wrapping my head around the issue. First off I think people use their smart phone for things that are best left to other devices. IMHO it is stupid what some people do with them. Surfing the web is at the top of my stupid list. [ I mean no offense to anyone, just my opinion ] From my research making them "mobile friendly" just requires something in the head of the page to tell small device browsers how to scale the page. I've looked at many of my pages on everything from an iPhone 4 to my netbooks. All of them scale very well. Even for my old eyes. I don't plan on doing anything. -- "The dog is a gentleman. I hope to go to his heaven, not man's." Mark Twain

Barry's fix makes it scale but also tells folks to dump their phones in the toilet cos this site is not built for phones. ... well, in so many words, nicely. LOL smile

I'm sorry, but I'm not going out of my way to make my Freepages site mobile friendly. It is what it is and it's staying that way! CAWTHORN, SCOTT,  & DeSILVA PALMER Family History Pages: http://freepages.genealogy.rootsweb.ancestry.com/~cawthorn/ temporarily at http://www.annmcclean.co.nf/ On 20/08/2018 04:27, Billie Walsh wrote: > I think we have just about beat this subject to death. But, I still > have a hard time wrapping my head around the issue. > > First off I think people use their smart phone for things that are > best left to other devices. IMHO it is stupid what some people do with > them. Surfing the web is at the top of my stupid list. [ I mean no > offense to anyone, just my opinion ] > > From my research making them "mobile friendly" just requires something > in the head of the page to tell small device browsers how to scale the > page. > > I've looked at many of my pages on everything from an iPhone 4 to my > netbooks. All of them scale very well. Even for my old eyes. > > I don't plan on doing anything. >

Nobody said you have to. Google will penalize sites that aren't... which is the only reason for me to do anything on it. Of course, then our sites went away.... lost Google ranking.... so.... shrug. LOLOL Back to site overhaul -- later guys!

Here's a page that gives a very clear explanation of the tag that makes sites "mobile friendly". https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag While not an "official" tag it solves the problem of screen size. It seems that "mobile friendly" relies on the high resolution of most small devices. The pixels on our regular devices are not the same as the smaller ones we use every day. It seems that modern smart phones have resolutions approaching the very best high definition television screens. Way better than our average computer monitor. That's the old issue. Anyway, it seems that if we put |<meta name="viewport" content="width=device-width, initial-scale=0.86, maximum-scale=3.0, minimum-scale=0.86"> in the head of the page we are now mobile friendly. | Here's Googles own view of the viewport tag https://developers.google.com/web/tools/lighthouse/audits/has-viewport-meta-tag https://developers.google.com/web/fundamentals/design-and-ux/responsive/ It appears to me that extraordinary measures to be "mobile friendly" are not needed. A simple meta tag takes care of it to even Google's satisfaction. Judy. Chill out. Go ahead and use your tables. Your working to hard. On 08/20/2018 05:26 AM, JFlorian wrote: > Nobody said you have to. Google will penalize sites that aren't... which > is the only reason for me to do anything on it. > > Of course, then our sites went away.... lost Google ranking.... so.... > shrug. LOLOL > > Back to site overhaul -- later guys! > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe and Archives https://mailinglists.rootsweb.com/listindexes/search/freepages-help > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > -- "The dog is a gentleman. I hope to go to his heaven, not man's." Mark Twain

Mobile friendly was not an issue I brought up as needing fixed. It already is fixed, for me. Barry gave the view tag to me long ago. It's already part of the template he created, nice and pretty at the top of every page. One thing I don't need to fix. smile

Judy, if you went to the Google pages I linked it tells you that the "viewpoint" tag is one of the things that Google looks for to make sure your page is "mobile ready" for better listings. On 08/20/2018 11:57 AM, JFlorian wrote: > Mobile friendly was not an issue I brought up as needing fixed. It already > is fixed, for me. Barry gave the view tag to me long ago. It's already > part of the template he created, nice and pretty at the top of every page. > One thing I don't need to fix. smile > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe and Archives https://mailinglists.rootsweb.com/listindexes/search/freepages-help > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > -- "The dog is a gentleman. I hope to go to his heaven, not man's." Mark Twain

Billie, Again, Barry **already** did the viewpoint tag for me when Google first announced this. Back in 2016 or 17 ? Again, I was answering someone ELSE. I do not have any issues about Mobile tags. J

I don't remember the exact quote but I seem to recall that you were doing all that hard work, removing tables etc., to get a better ranking on Google. The point I was attempting to make was not so much that your pages needed to be "mobile ready" but that what you were doing might not be needed for Google. Did I misinterpret? If so, I apologize. On 08/20/2018 02:03 PM, JFlorian wrote: > Billie, > > Again, Barry **already** did the viewpoint tag for me when Google first > announced this. Back in 2016 or 17 ? > > Again, I was answering someone ELSE. I do not have any issues about Mobile > tags. > > J > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe and Archives https://mailinglists.rootsweb.com/listindexes/search/freepages-help > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > -- "The dog is a gentleman. I hope to go to his heaven, not man's." Mark Twain

Hi Billie, I'm not doing the hard work for Google. I'm doing it because the site was a huge mess (too many prior webmasters using different backgrounds), and am learning External CSS. I converted all the freepages sites, but had this County site left to do. The site is over 6,000 files, and heavy on map images, photos, and huge tables. Table-wise, I thought I had to convert tables, too, to CSS. Instead now, I'm gonna focus on cleaning them up (mso tags, in line styles everywhere) and see how to make them just behave. Somewhere in a thread, someone asked about Mobile Friendly, which I answered. But all this hard work, that's so I'm not ashamed anymore of a mismatched site and can be proud of it when I pass it on. If my hands and tremors cooperate... and I quit double-tapping...and pain travels off on a vacation... maybe I'll be done by Spring (2 years since I started the conversion). Judy