If you change the garland theme so that the javascript it outputted at the end of the document, javascript doesn't load correctly.
Following these rules
http://developer.yahoo.com/performance/rules.html#js_bottom
http://wimleers.com/article/improving-drupals-page-loading-performance#r...
Built-in doesn't have this issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | a.zip | 10.99 KB | mikeytown2 |
Comments
Comment #1
psynaptic commentedAhh yes, I use JS at the bottom of my page too.
I've found that it works on my test site and on 1 live site although the script tags are not well formed like they are when they are in the head.
Can you describe the problem a little more so I can try and track this down?
Comment #2
mikeytown2 commentedUsing Javascript Aggregator, and Dhtml Menu as well.
http://drupal.org/project/javascript_aggregator
http://drupal.org/project/dhtml_menu
I can't think of any thing else that would effect it
Comment #3
psynaptic commentedI have installed DHTML Menu and Javascript Aggregator, enabled the permissions 'access administration pages' and 'administer site configuration' for anonymous users, set the JS aggregation to on and placed the administer menu in the left sidebar of Garland. JavaScript is still functioning for me with $scripts at the bottom as in Wim Leers' guide. I have tested in both Beautify and Compact modes of htmLawed.
It might be something else about your setup that's causing this. Can you explain more so we can try and track this bug down? Thanks.
Comment #4
mikeytown2 commentedI think it revolves around HTML and XHTML
I've disabled JS and it still gives me a very odd page layout on the Modules Page
in FF3 heres the view source
Here's the view generated source
Comment #5
mikeytown2 commentedlatest div fixes this. I think it does, anyway kinda a mute point since logged in doesn't see output, and the error is the most evident on the admin module page.
Comment #6
psynaptic commentedHi mikeytown2, thanks for the help.
It looks like the doctype is being added back wrongly. If that was the case then it wouldn't be just happening on the modules page. Can you have a look with anonymous users and see if you can see the doctype being put back in the wrong place, or anything that might help us sort this (unless it's fixed!).
Comment #7
mikeytown2 commentedI think it was the cache... JS appears to have stopped working again.
Comment #8
psynaptic commentedOh, that's a shame. Can you paste your HTML source again?
Comment #9
mikeytown2 commentedK figured this one out i think after doing a diff on the source...
Normal Output
Mod Output
Not 100% because the diff program had a lot of trouble with the files but, I think this is it.
Comment #10
psynaptic commentedThe seems to just remove a comment which wouldn't cause any problems.
Please post the source of your unprocessed and processed HTML. Thanks.
Comment #11
mikeytown2 commentedComment #12
mikeytown2 commentedComment #13
matthieuscarset commentedClosing this issue as not relevant anymore.