Using superscript in superscript and putting it in one hight-level defeats the second use of superscript in itself, right?
It’s really an astronomical issue to have…
Since our footnotes plugin produces superscript tags and numbers the footnotes it produces, you don’t have to and shouldn’t use supersscript (=<sup>) tags.
There is no ‘second use of superscript’.
There is only – for comparsion! – a “normal” number 1, which I superscripted manually; and there is a footnote 1), which is only superscripted by the plugin.
Nevertheless the footnote 1) is placed higher, than the number 1 – that the point.
OK. So what’s bothering you then?
You can always change the styling of the footnotes with our Custom CSS feature.
I like the position of my manually superscripted number 1; and I would like to have the same position for the automatically superscripted footnotes.
So, since the position of my manually superscripted numer 1 is determined by
sup {
bottom: 1ex;
}
– by what is the position of the automatically superscripted footnotes determined?
What have I to write into my reddle-child-theme style.css for changing the position of the automatically superscripted footnotes?
Hi,
here is the styling for our Footnotes superscript:
vertical-align: top !important;
position: relative !important;
top: -0.1em !important;
If you want to change the styling just type any CSS code in the Custom CSS text area of the Footnotes Plugin.
You can easily manipulate the styling of the Footnotes superscript. As an example:
.footnote_plugin_tooltip_text > sup { top: 0.3em !important; }
will move the superscript a few pixel to the top.
Thank you! Works.
0.5em produces the position, which I need. –
But why does it not work with:
.footnote_plugin_tooltip_text > sup { bottom: 1ex; !important; }
?
Hi 1a-spielwiese,
there is an error in your CSS code.
.footnote_plugin_tooltip_text > sup { bottom: 1ex<strong>;</strong> !important; }
Correction:
.footnote_plugin_tooltip_text > sup { bottom: 1ex !important; }
(take a look at the semicolon after 1ex)
Thank you again. – Without semicolon it works now.
Would be nice if you leave a review 🙂
