Difference between revisions of "Template:Ability (LW2)"
Jump to navigation
Jump to search
m |
m (That's visibility: hidden, not display: hidden; herp derp) |
||
Line 1: | Line 1: | ||
− | <div align="center"><div style="position: relative; top:15px;">[[File:{{{ s_image }}}|32px| {{{s_caption|}}}]]</div>{{ #ifexpr: {{{ b_info | | + | <div align="center"><div style="position: relative; top:15px;">[[File:{{{ s_image }}}|32px| {{{s_caption|}}}]]</div><div style="position: relative; left: 18px;{{ #ifexpr: {{{ b_info | 0 }}} || visibility: hidden; }}">[[File:Icon_Skill_Info.png|18px|{{{s_info|}}}]]</div></div>{{ #ifexpr: {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} | <div style="text-align: {{{align|center}}}; {{ #ifexpr: ( {{{ b_name | 1 }}} or {{{ b_descr | 0 }}} ) and not {{{ b_info | 0 }}} | position: relative; top: 18px; | }}"> {{ #ifexpr: {{{ b_name | 1 }}} | '''{{{s_name|PerkName}}}'''<br/> | }} {{ #ifexpr: {{{ b_descr | 0 }}} | ''{{{s_descr|PerkDescription}}}'' | }}</div> | }} |
<noinclude> | <noinclude> | ||
Line 22: | Line 22: | ||
The text also behaves if this template is instead used inside a subst: version of the Class_Tree template. It could be some weird issue with the parser/template-rendering-parsing-dohicky. | The text also behaves if this template is instead used inside a subst: version of the Class_Tree template. It could be some weird issue with the parser/template-rendering-parsing-dohicky. | ||
− | |||
− | |||
[[Category: Templates]] | [[Category: Templates]] |
Revision as of 20:17, 27 January 2017
[[File:{{{ s_image }}}|32px| ]]
PerkName
Skeleton: {{Ability_(LW2) | s_image = | s_caption = | s_name = | s_descr = | s_info = | b_name = {{{ b_name }}} | b_descr = {{{ b_descr }}} | b_info = {{{ b_info }}} }}
Bugs
If this template is used inside a Template:Class_Tree_(LW2) and b_info
is not true
, then for some blasted reason the text overflows the cells. With b_info
set, the text behaves and stays inside the table's cells as they should. (How very, very annoying.)
The text also behaves if this template is instead used inside a subst: version of the Class_Tree template. It could be some weird issue with the parser/template-rendering-parsing-dohicky.