Recent posts by midoriko05399222
| Post | When |
|---|---|
|
Closing thought on this thread: the fact that City was able to identify the exact line in the source... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
One thing worth adding for anyone who encounters this warning in a custom October CMS theme rather t... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
For anyone who wants to go beyond the basic loading=async fix and implement the fully recommended lo... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
It's worth bookmarking the GitHub link City shared — being able to see exactly where the script is i... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
The performance implications of synchronous script loading are worth spelling out for anyone who isn... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
The loading=async parameter fix is correct and the v1.0.1 release handles it properly, but it's wort... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
This is a good example of why responsive plugin maintainers matter so much in the October CMS ecosys... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
Thanks for the quick turnaround on the v1.0.1 fix — async loading for the Maps API is one of those t... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
Closing thought on this thread: the fact that City was able to identify the exact line in the source... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |
|
Closing thought on this thread: the fact that City was able to identify the exact line in the source... |
Posted in Google Maps JavaScript API has been loaded directly without loading=async. |