You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basic stuff, but makes a difference. At the moment the pages index, and the three jump to's (MessageIndex, Display and Search templates) have a colon forced in the markup. Examples:
This is something inherited from God knows where (probably YaBB) and is a right PITA for theming. Say someone doesn't want a colon there.
At the moment they have to hack index.template.php to get rid of the colon from span class="pages", and they have to hack the other three templates to get rid of it from the jump to's.
If the colon is moved to the text string (where it really should be anyway) people can change the presentation just by editing the string in the admin languages editor, or by editing one languages file if they prefer doing that (handy if a themer wants to use a custom theme string to redefine the default text).
(BTW, my 2c is that the jump to's look far better with just an nbsp; between the label text and the input)
The text was updated successfully, but these errors were encountered:
Note: IE8 and Opera 4-6 only support the old, single-colon CSS2 syntax (:after). Newer versions support the standard, double-colon CSS3 syntax (::after).
Note: For :after to work in IE8, a <!DOCTYPE> must be declared.
Basic stuff, but makes a difference. At the moment the pages index, and the three jump to's (MessageIndex, Display and Search templates) have a colon forced in the markup. Examples:
and:
This is something inherited from God knows where (probably YaBB) and is a right PITA for theming. Say someone doesn't want a colon there.
At the moment they have to hack index.template.php to get rid of the colon from span class="pages", and they have to hack the other three templates to get rid of it from the jump to's.
If the colon is moved to the text string (where it really should be anyway) people can change the presentation just by editing the string in the admin languages editor, or by editing one languages file if they prefer doing that (handy if a themer wants to use a custom theme string to redefine the default text).
(BTW, my 2c is that the jump to's look far better with just an nbsp; between the label text and the input)
The text was updated successfully, but these errors were encountered: