[Pro] Javascript for Search Field, Safari problems

Walter,

Separate but related question…

I agree with your sound reasoning about putting JS before instead of before , but why does your Protaculous2 action put a link to the large “prototype.js” file before ? Why not before instead? And why does Protaculous2 put “Additional JS Libraries” (which we type into the Actions palette) before ? Why not before ? Why does your Carousel2 action link to “scriptaculous.js” before ? Why does your ScriptyLightbox3 action link to “scripty_lightbox_3.js” before ? Is it a rule that all external scripts should be placed before ? Perhaps not in light of this…

Furthermore, I see a lot of Freeway-generated functions placed before too, including:

  1. FWShowHideLayer
  2. FWLoad
  3. FWRestore
  4. FWLSwap
  5. FWCallHit
  6. FWSlave
  7. FWFindLayer

I have “render blocking” in mind when I pondering these things, especially the external *.js files which Google’s PageSpeed Tools dislikes.

–James W.


dynamo mailing list
email@hidden
Update your subscriptions at: