A discussion yesterday interested and confused me enough that I decided to do a bit more digging around to find out what information I could pull up on the subject.An issue known as far back as late 2015 which affected only the Safari browser shrinking content onload, which had a specific width declared, was fixed by developers adding shrink-to-fit=no to the viewport meta tag. I think this must have escaped the attention of a number of developers, inclucing those at Bootstrap.Strangley Bootstrap has now included it in v4.2, (almost a year after the official realease of v4) when the Safari issue, according to some sources, is largely irrelevant now and has been for some time. Apple at some point between 9.2 and 9.3 reverted back to how their broswer worked before the issue surfaced.Persoanlly I have never used it and dont intend to going forward as I never use specific width containers, perhaps Bootstrap feels the need to include it late on, after the horse has bolted, because some deve
AdChoices