[UPDATE 2.0.8]
-
hello,
For me, the update is ok,
I had to make some modifications in the css to get the same rendering as I had before.
One thing doesn’t work though, it’s the Reduce by default function:
-
Thank you for your feedback and for making and sharing this new screen video.
For the default collapse to work, you need to leave the style attribute and its value placeholder in the
reference-container.htmltemplate:<div id="footnote_references_container_[[post_id]]" style="[[style]]">, so that task.php can print the hidingdisplay: nonedefault rule there if the setting is enabled, not if not.You add a speaker-mute class for the embedded screenreader not to read the reference container. Is that recommended for general implementation? If so, we’ll consider adding it.
Beside that, pulling the onclick events out of the spans, and moving them to the table cells, would enhance user experience because it suffices to click to the left of the footnote text. Precisely clicking on a symbol or a number is more complicated and therefore is only appropriate for inline footnote referrers, not for table cells with plenty of space left unused. The plugin’s templates and style sheet shipped from 2.0.0 on are designed on these lines.
As of the arrow placement with respect to the footnote number in the list, I needed to compose everything at PHP level because CSS seems to be lacking rules keeping together numbers, punctuation and symbols but allowing breaks after spaces. That has been fixed for v2.0.6, but placeholder backwards compatibility is restored since 2.0.7. Probably there should now be two templates to switch between wrt legacy layout, and a third for rtl strings with numbers, that flow ltr. Tables do reorder automatically. I’m afraid things have gotten screwed up, but arrows in an extra column seemed so unexpected that they’ve been dropped and caused the major version number to increment, before coming back prepended (2.0.3).
Only one thing more: The <a> element enclosing the <sup> footnote referrer remains in
footnote.htmlso that the theme-specific default link color applies, because that is widely preferred. If desired, a rule can be added to Custom CSS to make its color inherit text color. Wrt themes defaulting links to underline, the footnote referrers need to be exempted. That will be fixed in 2.0.9.Please feel free to post any requirements fit for default styling.
I apologize again for the bug that I introduced, and didn’t identify until yesterday (https://ww.wp.xz.cn/support/topic/change-the-position-5/page/2/#post-13630114).
Thank you very much for assistance and contribution.
Best regards,
@pewgeugesThanks a lot for the correction, it works perfectly with the reinsertion of style=”style.
The speaker-mute class is useful for users of the speaker plugin which allows to read the text but not for others. No problem for me, I can integrate it manually in the code at each update.
Concerning the click zones, it’s true that it’s less precise with my modifications. I was inspired by what Wikipedia does.
A large click zone sometimes gives the impression that we don’t know which link we are on. With a little css, you can make an underline to emphasize the zone, but I don’t like the underline here.For the < a >, I removed it not for the color but because I’m superstitious about SEO, even if there is no href, I’m afraid it plays a negative role on the page. No proof to that, just a belief ^^.
Question : does this play a role for the functioning of the plugin ?
Because for double notes, a click on the second note has no effect.
Thank you very much for your feedback. Sorry for being late. I’m glad that you solved the problem.
To your question: Since 2.0.4, the <a></a> around the <sup></sup> of the footnote referrers plays no role in the plugin’s functioning. The link addresses, added with the element for 2.0.0 to get the intended interactivity to keep working when JavaScript is disabled, have been removed on user request to stop cluttering the browsing history that the back button relies on.
Footnote referrers in the theme’s link color are currently requested and are meeting user expectations. For that to happen, the <a> element needs to be in the template. Using link, hover, active and visited as named color variables would be handy, but AFAIK these exist as pseudo-class names only, and CSS is lacking that feature, so we have to use the actual element for mere styling.
I’ve never heard or read that these <a> elements would affect page ranking, but your point about SEO is very concerning. It seems there is not much information available (https://moz.com/blog/how-many-links-is-too-many). But I think that search engines don’t care when there is no actual URL to add to the list, and won’t be going to count elements, do they?
The malfunctioning of combined notes is indeed the major remaining bug. This one needs to be fixed before we can go on and add settings. We have a request for named notes, like on Wikipedia so as not to copy-paste notes into multiple instances. Usual algorithms re-use the note number, and the backlinks are small letters. By contrast, this plugin keeps numbering, so that visitors have a clue about where they left off, and could get back if the algorithm followed through by making the enumerated numbers individual backlinks. The downside is that when the tooltips are disabled, visitors have no clue about whether a footnote referrer points to a new note or an already known one.
Whatever system is used, re-using footnotes in a web page is probably one of the worst mistakes in user experience design. I think of re-used notes in a web page as a failure to transpose to the internet a practice that is very convenient in print publishing, where the number of pages matters.
There is a point about getting each footnote unique; for shortness just a link: https://ww.wp.xz.cn/support/topic/image-caption-21/#post-13611971 Therefore we need to assess what is best, but hopefully the plugin will be debugged anyway.
Thanks for explaining the speaker-mute class. Not reading the notes list out of context makes sense, and the class name is probably added also by the Speaker WordPress Plugin from Merkulov parsing the shortcode [speaker-mute], and the related Speech Synthesis Markup Language is supported by the W3C. The class is being added to the
reference-container.htmltemplate.The question is where. For consistency, I’d add it to the outer
reference-container-wrapperdiv (class name is now shorter), added to keep together the heading and the references table in print, when they tend to fall apart because unlike a stack of divs, a table fitting into a page gets hardly a page break (at least I didn’t find any rule).You make a good point about clicking zones, and the plugin already supports the hover-underline of the footnote number that the active backlink points to the footnote referrer of. I didn’t think that the point about ease of use does not always coincide with improved user experience. Yet, on docteur-fitness.com, with the nicely animated underline of inline hyperlinks and the fairly spacy layout, if there were no need to precise-click two times per note, I think that your visitors would greatly appreciate. With or without underline.
Thanks a lot for your response, I’m releaved that we can be sure that the extra <a> elements are not a problem.
When editing again, across the deadline, I mentioned that there should be a setting for whether or not <a> elements are used for styling purposes. The easiest way will be to ship the plugin with a dozen or so templates to switch between.
Thank you for your rating!
Best regards.
The topic ‘[UPDATE 2.0.8]’ is closed to new replies.
