Urgent unreleased bugfix version 2.5.12 with Stable Tag 2.5.10.

= 2.5.12 =
- Update: Scrolling: CSS-based smooth scroll behavior (optional), thanks to @paulgpetty and @bogosavljev issue reports.
- Bugfix: Backlinks: reflect scroll functions down/up differentiation across the template set, thanks to @bogosavljev bug report.
- Bugfix: Referrers: Hard links: enforce scroll offset with '!important' property for surroundings specifying otherwise, thanks to @bogosavljev bug report.
- Bugfix: Forms: prevent inadvertently toggling input elements with footnotes in their label, by optionally moving footnotes after the end of the label.
- Bugfix: Forms: prevent inadvertently toggling input elements with footnotes in their label, by optionally disconnecting those labels.
- Bugfix: Scroll offset: correct syntax error in the main style sheet.
- Bugfix: Reference container: correct new syntax errors in the 8 reference container row templates.
- Bugfix: Reference container: correct a new typo in the JavaScript reference container template.
- Update: Dashboard: General settings: split a dedicated 'URL fragment ID configuration' metabox off the 'Scrolling behavior' metabox.

git-svn-id: https://plugins.svn.wordpress.org/footnotes/trunk@2501451 b8457f37-d9ea-0310-8a92-e5e31aec5664
This commit is contained in:
pewgeuges 2021-03-23 04:02:07 +00:00
parent ce42420149
commit 9e8e28412e
36 changed files with 326 additions and 132 deletions

View file

@ -5,17 +5,12 @@
* Created-Date: 15.05.14
* Created-Time: 16:21
* Since: 1.0
*
* @version 2.5.11
* @lastmodified 2021-03-20T0323+0100
*
* Classes recommended for Custom CSS:
* @see templates/dashboard/customize-css-new.html
*/
/**
*
* System of unified minified style sheets tailored to the needs of the instance.
*
*
* - Update: Stylesheets: increase speed and energy efficiency by tailoring stylesheets to the needs of the instance, thanks to @docteurfitness design contribution.
* - Bugfix: Stylesheets: minify to shrink the carbon footprint, increase speed and implement best practice, thanks to @docteurfitness issue report.
*
@ -29,30 +24,27 @@
* @link https://wordpress.org/support/topic/simply-speed-optimisation/
*
* Six development stylesheets are concatenated to 12 unified stylesheets.
* @see development/csscat.sh
* Once these are minified, the temporary files are deleted to streamline
* the plugins codebase.
* The stylesheet file names consist of "footnotes-" and a code showing
* which additional stlesheets enter into its composition:
*
* The unminified development stylesheets are distributed for reference.
* Their minified versions are included for consistency and convenience.
*
* A production stylesheet file name consists of "footnotes-" and a code
* showing which additional stlesheets enter into its composition.
*
* The first part of the code contains 4 letters showing whether tooltips
* are enabled, and if so, which implementation: AMP, alternative or jQuery:
* ampt AMP compatible tooltips dev-tooltips.css & dev-amp-tooltips.css
* altt alternative tooltips dev-tooltips.css & dev-tooltips-alternative.css
* jqtt jQuery tooltips dev-tooltips.css
* nott no tooltips -
*
* The second part of the code consists of the 4 letters "brpl", for
* Basic Responsive Page Layout, followed by a digit showing if a fix
* is applied, and if so, which one:
* 0 -
* 1 dev-layout-reference-container.css (only)
* 2 dev-layout-entry-content.css post without title
* 3 dev-layout-main-content.css title and post
*
* The dashboard stylesheet is minified as-is.
* @see css/settings.css
*
* are enabled, and if so, of which implementation:
* ampt AMP compatible tooltips dev-tooltips.css & dev-amp-tooltips.css
* altt alternative tooltips dev-tooltips.css & dev-tooltips-alternative.css
* jqtt jQuery tooltips dev-tooltips.css
* nott no tooltips -
*
* The second part of the code consists of the initialism of
* Basic Responsive Page Layout, followed by a digit showing
* if a fix is applied, and if so, which one:
* 0 -
* 1 dev-layout-reference-container.css footnote list only
* 2 dev-layout-entry-content.css post without title
* 3 dev-layout-main-content.css title and post
*
* @since 2.0.0 various.
* @since 2.0.0 Referrers: vertical align: lower from top: 0.4em to top: 0.6em
* @since 2.0.0 Tooltips: Font size: set to inherit instead of 13px
@ -135,14 +127,13 @@
* word-wrap: anywhere;
* word-break: break-all;
*
*
* - Bugfix: Reference container, tooltips: URL wrap: enable the 'word-wrap: anywhere' rule, thanks to @rebelc0de bug report.
*
* @since 2.5.4
*
* @reporter @rebelc0de
* @link https://wordpress.org/support/topic/footnotes-on-mobile-phones/#post-14037101
*
* @since 2.5.4
*
* These rules turn out useless for the purpose and are commented out:
* word-wrap: break-word;
* overflow-wrap: break-word;
@ -155,16 +146,25 @@
}
/**
* Optional hard links: anchors with scroll offset
* Optional hard links: anchors with scroll offset.
*
* - Adding: Referrers and backlinks: optional hard links for AMP compatibility, thanks to @psykonevro issue report, thanks to @martinneumannat issue report and code contribution.
*
* @since 2.3.0
* @contributor @martinneumannat
* @link https://wordpress.org/support/topic/making-it-amp-compatible/
* @reporter @psychonevro
* @link https://wordpress.org/support/topic/footnotes-is-not-amp-compatible/
*
* @contributor @martinneumannat
* @link https://wordpress.org/support/topic/making-it-amp-compatible/
*
* @since 2.3.0
*
* - Bugfix: Referrers: Hard links: enforce scroll offset with '!important' property for surroundings specifying otherwise, thanks to @bogosavljev bug report.
*
* @reporter @bogosavljev
* @link https://wordpress.org/support/topic/compatibility-issue-with-wpforms/
*
* @since 2.5.12
*
* Although often skipped as unstraightforward, or believed impossible,
* an offset hard link anchor can be coded out of a fragment identifier
* span with absolute position nested in a span with relative position.
@ -172,12 +172,12 @@
.footnote_item_base,
.footnote_referrer_base {
position: absolute;
position: relative !important;
}
.footnote_item_anchor,
.footnote_referrer_anchor {
position: relative;
position: absolute !important;
}
/**
@ -285,9 +285,9 @@ Classes:
/**
* Reference container label.
*
*
* - Bugfix: Layout: support right-to-left writing direction by replacing remaining CSS values 'left' with 'start', thanks to @arahmanshaalan bug report.
*
*
* @since 2.5.8
* @reporter @arahmanshaalan
* @link https://wordpress.org/support/topic/right-to-left-text-problem/
@ -357,16 +357,16 @@ table
}
/**
* Table caption.
*
* Table caption for accessibility.
*
* - Bugfix: Reference container: apply web semantics to improve readability for assistive technologies, thanks to @derivationfr issue report and code contribution.
*
* @since 2.5.11
*
* @contributor @derivationfr
* @link https://wordpress.org/support/topic/enhance-accesibility-by-using-instead-of/
* @link https://a11y-101.com/development/tables
*
* @since 2.5.11
*
* The table caption must be present for screen readers but may be hidden to sighted users.
*/
@ -381,22 +381,22 @@ caption.accessibility {
/**
* Footnotes list.
*
*
* - Bugfix: Reference container: no borders around footnotes, thanks to @ragonesi bug report.
*
*
* @since 2.0.0
* @reporter @ragonesi
* @link https://wordpress.org/support/topic/thin-box-around-notes-in-reference-container/
*
*
* - Bugfix: Reference container: enforce borderless table cells, thanks to @ragonesi bug report.
*
*
* @since 2.0.1
* @reporter @ragonesi
* @link https://wordpress.org/support/topic/box-around-c-references-container/
*
*
* - Bugfix: Layout: support right-to-left writing direction by replacing remaining CSS values 'left' with 'start', thanks to @arahmanshaalan bug report.
* - Bugfix: Layout: support right-to-left writing direction by enabling mirrored paddings on HTML dir="rtl" pages, thanks to @arahmanshaalan bug report.
*
*
* @since 2.5.8
* @reporter @arahmanshaalan
* @link https://wordpress.org/support/topic/right-to-left-text-problem/
@ -541,8 +541,8 @@ Link color set to inherit, so referrers/numbers are not grayed out.
* have all their rules moved to settings.css so as to alleviate
* the common stylesheet. Still these rules are only used if the
* Footnotes ad link logo is present in the page footer per user
* dashboard setting. Making these rules conditional like those
* pertaining to tooltips, either jQuery or alternative, would
* dashboard setting. Making these rules conditional like those
* pertaining to tooltips, either jQuery or alternative, would
* double the number of united minified stylesheets shipped with
* the plugin. Hence these are present by default at the bottom.
*