And if you want to lock down what kinds tags can run on your site, they have a nice whitelisting/blacklisting system that lets you block capabilities (e.g. customScripts to block arbitrary JS):
Thanks for those links. Am I missing something in them or would using managing GTM programmatically via their API kind of defeat the entire purpose of giving business users like myself the ability to add/manage tags?
Seems like a case where there's no good way to have our cake and eat it too in terms of usability for business users and testing/security for our engineers.
How do you know that Chrome and Safari are supported? Is there some documentation of this? A list somewhere? If so, Facebook should at least link to that page from here.
No surprise there; Opera's market share is small enough that FB can simply code to the standard and worry about explicitly supporting the major browsers.
Although interestingly, if Opera accounts for ~2% of FB users (big if), then FB would have 16MM Opera users. Using the average of $4/user/year, that means Opera generates $64MM for them. That would be more than enough to justify throwing a few devs at.
Edit: Also curious is the pointless URL that page has. I would have thought FB would be using basic SEO on their help pages, so that someone googling "facebook supported browsers" would have a better chance at ranking first (it does for me, anyway). As an aside, the sub's page is actually the second result.
I would actually posit that they make much less money per user from Opera than IE.
Ie the type of individual who would click FB ads (or spend money on virtual gardens) is more likely to use the Windows default browser.
Because chome is 1. quite new and 2. auto-updating without neither asking or notifying users (and that is G-R-E-A-T).
Safari I don't know, are FB obligated to inform people of every possible choise? Nope, they aren't. Now let's discuss something more interesting than this dull facebook page!
> Because chome is 1. quite new and 2. auto-updating without neither asking or notifying users (and that is G-R-E-A-T).
You know that, but there's no guarantee whatsoever that someone landing on this page knows that.
It's in FB's best interest to inform people of what works and what doesn't. They certainly don't test every single browser out there, so putting the browsers they test on onto this page keeps users on the happy path.
But, bear in mind that the iPhone was only ANNOUNCED in 2007, not developed - in fact rumors of an iPad-like device (the basis of the iPhone interface) were circulating for almost a decade prior to the iPhone's announcement. During that time, Schmidt was on the board of Apple, and was certainly in a position to benefit from knowledge of Apple's mobile strategy.
So in short, it is plausible and likely that Apple began working on a touch screen phone years before Google even considered purchasing Android.
And correct me if I'm wrong but, weren't the early models of Google's phone based on a blackberry-like design with a half screen / half keyboard front? And wasn't it not until Apple unveiled the iPhone that Android began to take on its present form?
Those people help make the web possible, and the web is a beautiful, world changing thing. I hope it won't be this way forever, but right now ads are part of the web's infrastructure; they pay the bills.
https://developers.google.com/tag-manager/api/v1/
And if you want to lock down what kinds tags can run on your site, they have a nice whitelisting/blacklisting system that lets you block capabilities (e.g. customScripts to block arbitrary JS):
https://developers.google.com/tag-manager/devguide?hl=en#res...