#3185 closed enhancement (no action required)
presentational elements in text strings
Reported by: | hnla | Owned by: | |
---|---|---|---|
Milestone: | 1.5 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Templates | Keywords: | |
Cc: |
Description
Could this practice be curtailed?
{{<a class="show-hide-new" href="#post-topic-reply">↓ New Reply</a>}}
'↓' is not good practice, it's a presentational issue and proves fiddly to remove as it's part of the subnav - it should be left to the frontend to apply this.
Change History (4)
#2
@
13 years ago
Sorry, my bad. Not sure why I thought they were hardcoded in core, must have been a flashback to summit else.
Note: See
TracTickets for help on using
tickets.
Those symbols are no harder than anything else in BP-Default to change. These were in the templates, not in a function in core and, as you know, can be addressed in a custom theme.
However, we've taken out the down-arrows in r4322 because they were inconsistent with the rest of BP-Default.