Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #1 – September 13, 2015, 05:15:16 pm
They are all like that ... just another leftover I'd say. I'll kill them in 1.1 and see what happens, if we are lucky some cats will die. ETA: Lucky day, dead cats resulted
Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #2 – September 13, 2015, 05:29:16 pm
Sounds good. Feral cats are a real problem in Australia. Now if you can figure out how to massacre cane toads by editing forum markup that'd be really good. (actually I could probably think of cleaner css for the linktree)
Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #4 – September 13, 2015, 05:42:34 pm
Ah, ok. There's probably a way around that. I'm also thinking it should be possible to get rid of some of the excessive padding on the li's, so that the anchors can fill more of the space (fewer missed clicks, especially on the home icon). Will give it some thought.
Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #6 – September 13, 2015, 05:51:28 pm
Which file holds the sources stuff for the linktree?
Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #7 – September 13, 2015, 05:53:27 pm
index.template in the function theme_linktree
Re: It's pink, therefore it's Span. Why for span in linktree?
Reply #14 – September 13, 2015, 07:09:00 pm
Aha. Got it. Reason I couldn't find any extra_before is because it isn't used anywhere. Possible candidate for deprecation? There's only one instance of extra_after, and that's in Memberlist.controller.php. No other files appear to use it anywhere, AFAICT. ETA: Here's a thought. If these aren't being used except for the added memberlist shiz, is it even worth keeping them? Much less hassle on mobile if they aren't there. The stuff on the memberlist could just be generated as part of the standard anchor, if you think it's necessary to have it at all.