We build a payment plugin and currently working on the release on the Shopware store. One of the feedback we got is to either add async or defer to the externally loaded <script>
The difference between the two is simple once it is understood but before that it sounds the same – and it is not at all and breaks your page if you do it wrong – be there, done that (thankfully while testing).
Both (defer and async) tell the browser to load the script non-blocking, so the browser will continue loading the document and parse the DOM to render everything. But the big difference is:
async attribute is present then the scripts and all their dependencies will be fetched in parallel to parsing and evaluated as soon as they are available.defer attribute will prevent the DOMContentLoaded event from firing until the script has loaded and finished evaluating.TL;DR both make scripts load in parallel to the DOM, but defer makes the DOMContentLoaded event to wait until the script is loaded and executed! That means for the context of Shopware, that our Shopware.PluginManager is waiting for the scripts.
If we use async, the Shopware.Plugin might execute before the script is loaded and end in "YourExternalVariable" is undefined errors.
If your bitbucket shell runner is doing weird stuff, you might have started the runner two times – in my case under different users (root + winkelwagen) and therefore it didn’t show up when looking for the screen.
I setup a proxy pass to have the app on one server and the hostname terminate by DNS on another machine. Setting up a reverse proxy is pretty easy: But for some reason, Safari doesn’t like the response. The important part is to NOT pass the Upgrade header on to the backend machine – don’t […]
Today I learned, one can use JSON in Magento 1’s layout xml. Tell Magento which action parameter are json and that’s it. You can tell Magento that only one parameter is json, like this. Then Magento decodes the json and uses it. I was very lucky to see it today, because I needed an array. […]
