It is just killing me that the garland page.tpl.php doesn't have an id (or even a distinctive class) for the content div. The default page.tpl.php (in the modules/system folder) adds an id="content-content", which woudl make jQuery targeting much cleaner.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | garland.patch | 765 bytes | starbow |
| #5 | content_types.patch | 1.21 KB | starbow |
| #1 | garland.patch | 765 bytes | starbow |
| garland.patch | 4.08 KB | starbow |
Comments
Comment #1
starbow commentedOops, bogus patch.
Comment #2
dvessel commentedHow about something other than "garland-content"?
The default in "modules/system/page.tpl.php" uses "content-content" while still a little odd, I think it's better than using the theme's name. Or maybe just "main-content" would be fine.
Comment #3
starbow commentedI don't really care what the id is. The only thing is that it needs to be something no one in the world is already using as an id in their content (two id's with the same name in the same page is a no-no).
Comment #4
dvessel commentedWell, the rest of us do. With the coming of Drupal 7 we will try to standardize on ID's and classes. "garland-content" is guaranteed to be changed when that happens. It's not semantic. Period.
Choose a good ID now and there's less chance of it being changed, and anything depending on it also.
Comment #5
starbow commentedOk, since there has obviously been thought put into the page.tpl.php file in the system folder, I will assume 'content-content' is the right answer.
Comment #6
dvessel commentedWell, thanks.
Comment #7
keith.smith commentedI'm confused. Is the patch in #5 right? It seems unrelated (or else *way* over my head in relation to this issue).
Comment #8
dvessel commentedAh!! sorry. I didn't even look.
Comment #9
starbow commentedOn the plus side, I was wondering what happened to my content_types patch :)
Here is the right one for this issue.
Comment #10
starbow commentedComment #11
drawk commentedComment #12
dpearcefl commentedIs this issue fixed in the latest D6? is there any interest in pursuing this issue?
BTW: Your patch needs to be named properly for it to be accepted.
http://drupal.org/node/1054616
Comment #13
dpearcefl commentedComment #14
sunIt's too late for markup improvements in D6.