@markhillyer
Both lines can be removed by adding this code in Footnotes’ Custom CSS:
.footnote_container_prepare > p {
border-bottom: none !important;
}
Alongside I need to add that Footnotes’ Custom CSS is now under a dedicated tab, as it was when this setting was added for v1.3.0. To improve its usability, it has now its own tab again, but that required to make it a new setting, and leave the legacy Custom?CSS text area at the bottom of the “Referrers and tooltips” tab, previously labeled “Customize” because of the Custom?CSS that it was added for. But after many other settings were added under the same tab, the tab label became a misnomer, confusing users who are strict about distinguishing between customization and configuration. Since best industry practice is to avoid customization, the tab label couldn’t be left as-is. Nevertheless Custom?CSS keeps its label because it is on the borderline between customization (it’s code) and configuration (it’s edited and stored in the settings). But it absolutely needs an extra tab, because it may involve a trial-and-error with repeated edits, so a dashboard cannot require to scroll down each time, as saving reloads the tab.
For these reasons, Footnotes’ dashboard has been set up (since 2.2.2 and current 2.2.3, released in the wake) to migrate Custom?CSS to a dedicated tab. You are already using Footnotes’ Custom?CSS, so this may be important to you.
We’re suggesting to all Footnotes users using the integrated Custom?CSS to proceed as follows:
- Open Footnotes’ settings.
- Click on the “Referrers and backlinks” tab.
- Scroll to the container labeled “Your existing Custom?CSS code” at the bottom of the tab.
- Cut or copy the content of the text area to the clipboard.
- After cutting the code, click on the Save button. That helps streamline the process, but emptying the text area is not required at any point.
- Click on the “Custom CSS” tab.
- Paste the code from the clipboard into the second, lower, big text area in the container labeled “Custom?CSS”.
- Click the Save button. If the small upper text area (in the container labeled, again, “Your existing Custom CSS code” yielding the same as under the other tab, but read-only) is empty or nearly empty, you may check the box “Custom?CSS migration complete”.
When the Custom CSS tab is saved with the box checked, both legacy containers are going to disappear. This one will first stay, and the box can still be unchecked. When it is saved again after unchecking the box, it will disappear but show up again when the tab is reloaded (by clicking on the tab or the Save button).
From upcoming v2.2.4 on, if the “Custom?CSS migration complete” check box is checked and saved, any remaining code in the legacy Custom?CSS instance will not be inserted in the header of the public pages any longer. That prevents bugs should any code be obsoleted. Best is to empty the field to streamline the storage container content.
v2.2.4 is scheduled for release today because it contains an urgent bugfix consisting in moving the backlink symbol selection setting back to the tab that it was previously under. A rigid data structure prevents redesigning the UI as needed. Despite the label that the forum engine decks me out with, I’m not the plugin author, and I’m only discovering how the well-designed specification from the plugin author was coded, very properly and following high coding standards.
As much about Footnotes’ Custom CSS, that you may use to fix your issue along these lines.
???
The CSS rule mentioned above is designed to eliminate the horizontal line beneath the Reference Container Heading, and it eliminates the additional horizontal line before the text too. Both lines at once because they are basically the same. The paragraph element that the reference container label was, is cut in two parts by the heading?2. The <?p?> start tag is closed by the browser to an empty paragraph before the heading, and the stray <?/p?> end tag after the heading is completed to another empty paragraph. That handling conforms to the spec including HTML5. Both empty paragraphs have the block display stipulated in the plugin’s public style sheet, and the bottom border therein:
.footnote_container_prepare > p {
border-bottom: 1px solid #aaaaaa !important;
}
Thank you very much for drawing our attention on this issue highlighting that two other settings are missing from the plugin’s dashboard: one for the reference container label bottom border, and another one for the reference container label element.
We apologize for the lack of these settings. Given you are already holding a solution for your website, the settings shall be added soon after the upcoming urgent bugfix 2.2.4.
Best regards.
