Closed sailKiteV closed 4 months ago
There was a related issue, the solution to which may have accidentally contributed to the behaviour described in this issue: #102
The triple-dot setting button will be positioned within the overall statblock container, such as:
The triple-dot setting button is positioned relative to the note container or other intervening ancestors with the appropriate position value:
position
Open sandbox vault
Restricted mode
Settings -> Core plugins
Fantasy Statblocks
statblock
~~~statblock creature: Adult Black Dragon ~~~
1.5.8 and 1.5.8
4.0.9
The following CSS is one possible solution to the problem, and was used to produce the image in the Expected Behaviour section:
/* may be worth using .block-language-statblock instead */ .statblock-plugin-parent { position: relative; } .statblock-plugin-parent .icons:has(> .setting-editor-extra-setting-button) { left: var(--size-2-2); }
I think I intentionally put it over there, but I can't recall the exact reason lol
I agree that it looks better closer. I'll try to roll this in with the next update, unless you're willing to PR :)
Check for existing bug reports before submitting. #
There was a related issue, the solution to which may have accidentally contributed to the behaviour described in this issue: #102
Expected Behaviour #
The triple-dot setting button will be positioned within the overall statblock container, such as:![statblock bug 1-1](https://github.com/javalent/fantasy-statblocks/assets/75286796/a5cab062-1e3f-445c-9663-88816f773aa5)
Current behaviour #
The triple-dot setting button is positioned relative to the note container or other intervening ancestors with the appropriate![statblock bug 1-2](https://github.com/javalent/fantasy-statblocks/assets/75286796/d7d80dc9-a982-4c55-ac90-ee919b48fe05)
position
value:Reproduction #
Open sandbox vault
.Restricted mode
if require inSettings -> Core plugins
.Fantasy Statblocks
from the plugin store.Fantasy Statblocks
inSettings -> Core plugins
.statblock
codeblock into the note, such asWhich Operating Systems are you using? #
Obsidian Version Check #
1.5.8 and 1.5.8
Plugin Version #
4.0.9
Confirmation #
Possible solution #
The following CSS is one possible solution to the problem, and was used to produce the image in the Expected Behaviour section: