Posting as I play...
1) Recompiling my style under core2 requires editing a couple of properties and that's it. Yay for not having the double negative variable naming for turning off custom comments pages :)
2) My current style, using core1, is using the new views array and so has extra items in the menu bar. Cute.
3) No overall div for the sidebar created by the sidebar primary function. Looking at core, I see it's in the page print, function. I would suggest that anything which is printing out a lognical grouping of content like that ought to print out the containing tags for that grouping itself, but that's personal preference - I doubt it'll make people override.
4) No CSS class to indicate the current view on the views list.
5) The tell a friend button on the userlinks toolbar isn't transparent like the rest.
6) While we're building in tags functionality, how about a tags_cloud function for the sidebar?
7) The basic comments layout is displaying with the userpic on its own line, which is annoying. Might be a width issue, but it never used to do that.
8) There is an unclosed h3 tag on the day page.
9) Page summary on Friends Page doesn't list the journal the entry's held in. (You can pinch the code for this from my style if you like - I just modded the existing Core2 stuff).
10) No tag counts as tool tips on tag links
11) For consistancy's sake, can the Reply link have brackets around it like the (Parent) and (Thread) links for comments?
Obviously, not all of these are bugs - some of them are things which I think are going to cause a large percentage of style authors to override the core functions.
1) Recompiling my style under core2 requires editing a couple of properties and that's it. Yay for not having the double negative variable naming for turning off custom comments pages :)
2) My current style, using core1, is using the new views array and so has extra items in the menu bar. Cute.
3) No overall div for the sidebar created by the sidebar primary function. Looking at core, I see it's in the page print, function. I would suggest that anything which is printing out a lognical grouping of content like that ought to print out the containing tags for that grouping itself, but that's personal preference - I doubt it'll make people override.
4) No CSS class to indicate the current view on the views list.
5) The tell a friend button on the userlinks toolbar isn't transparent like the rest.
6) While we're building in tags functionality, how about a tags_cloud function for the sidebar?
7) The basic comments layout is displaying with the userpic on its own line, which is annoying. Might be a width issue, but it never used to do that.
8) There is an unclosed h3 tag on the day page.
9) Page summary on Friends Page doesn't list the journal the entry's held in. (You can pinch the code for this from my style if you like - I just modded the existing Core2 stuff).
10) No tag counts as tool tips on tag links
11) For consistancy's sake, can the Reply link have brackets around it like the (Parent) and (Thread) links for comments?
Obviously, not all of these are bugs - some of them are things which I think are going to cause a large percentage of style authors to override the core functions.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}