Hello,
Thank you for your feedback and future modifications.
I will pay attention to your recommendation concerning this point: .footnote_plugin_tooltip_text {
top: 0.6em !important;
vertical-align: top !important;
position: relative !important;
}
For the collapse button’s vertical align , this is a detail 🙂 but if there is an option to set it why not;
Can we add, as an option, the nice dashed line delimiting references in the container?
>> Sure 🙂 with great pleasure
Hello @docteurfitness
Many thanks for your reply and agreement!
The overdue disabling of the comma in enumerations of backlinks is now effective and available in our new 2.1.4d4 bugfix development version currently at https://downloads.wordpress.org/plugin/footnotes.zip
It is compatible with the future settings for separators and terminators among an eventually rather long list to choose from and, instantly the most important, the option “none”—currently the only available, given the positive settings need more development and shall be ready prior to the release.
Additionally, an optional line break <br /> is available for insertion before each added backlink in an enumeration when combining identical footnotes is enabled. This option, defaulting to No, is available under the Settings tab > Reference container > Stack backlinks when enumerating. It should provide the needed layout fix when vertical enumeration is preferred.
This probably last development version before our 2.1.4 release is designed to assess whether all parameters are safe for seamless transitioning at our next updates, so that you are done with maintaining templates, scripts and style rules.
I apologize again for the hefty disruption that sometimes occurred during Footnotes’ upgrading process.
But—there is this bug on mobile phones you reported in https://wordpress.org/support/topic/update-2-1-3/#post-13713665. It affects only real devices, given in Chrome’s emulator on desktop the click functions work well in autoload too. How could that happen?
Do you still see this bug?
Best regards,
@pewgeuges
Hello
REFERENCE disapear : https://i.ibb.co/K91FQ3f/Sans-titre-2.jpg
because of this css
.footnote_container_prepare>p {
overflow: hidden !important;}
https://i.ibb.co/ZXBGSpx/Sans-titre-3.jpg
It’s possible that it comes from my margin and padding which are not good, I didn’t dig much.
apart from that it’s perfect 🙂
Otherwise for the bug on smartphone, I don’t know where it comes from.
I re-downloaded the old versions to check but all of them have this bug. Do you also see it with your smartphone ?
Hello,
Sorry for my late reply.
Do you also see it with your smartphone ?
Not yet; I scrambled to set up a test environment but failed because my SIM seems incompatible and my router’s WLAN is not accepted. I’ll check later in a hotspot.
I re-downloaded the old versions to check but all of them have this bug.
Thank you for taking this trouble. Is it possible that mobiles are served very early cached versions of every URL so that the bugfix is not in the page?
The only way to view a page source on mobile seems to be to manually type view-source: in front of the URL.
REFERENCE disapear : https://i.ibb.co/K91FQ3f/Sans-titre-2.jpg
because of this css
.footnote_container_prepare>p {
overflow: hidden !important;}
https://i.ibb.co/ZXBGSpx/Sans-titre-3.jpg
Thanks for reporting this! That rule is now deleted.
apart from that it’s perfect 🙂
Thank you for letting us know! So it’s good to go. For the comma removal to stay effective, you’d need to save the Settings tab of Footnotes’ dashboard, because in the release, I think the default will be reverted to comma for backwards compatibility. Only the full stop, discarded after footnote numbers as not localizable (should be optional) in 2.0.6, will probably remain on none, but both shall become customizable by selecting from a list. I wonder, though, whether two text boxes would not be more appropriate. Or do both and follow the scheme chosen for the arrows. Unless other feedback, we’ll discuss it on the project.
I’ll try to look into what’s going on with footnotes in autoload on smartphones!
-
This reply was modified 5 years, 6 months ago by
pewgeuges.
@docteurfitness
I get the same bug and the page source is the same. (It only took logging in for the WLAN to work.)
Did you test on iOS? If it works there, the issue would boil down to a browser bug.
-
This reply was modified 5 years, 6 months ago by pewgeuges.
Hello 🙂
I don’t have an iPhone, I’ll see tomorrow if someone has one at the office 🙂
Hello,
Thank you! Autoload seems to be so fragile a feature I can’t seem to be able to set it up in a sandbox despite applying recommended procedure. So I can imagine some browsers not fully dealing with it.
As of the comma setting, we don’t know yet how it will be designed: none in a long—or small—selection, or No in an extra Boolean. (You won’t be impacted by an added text box, though.)
After all, the opposite might be true: Some things working on Android but not on the iPhone? (Just a hint to your company.;)
@docteurfitness
We’ve updated our new developmennt v2.1.4d5 available at https://downloads.wordpress.org/plugin/footnotes.zip and the settings have indeed changed: You now need to register the No for the select box “Add a separator when enumerating backlinks:”, that defaults to Yes. This is probably user-friendlier than having just an option “none” among punctuation marks in the (now) second select box in a row. A text box to input a custom character or string is also present, for users writing in other languages or preferring special typography.
We wanted to make sure that updates are seamless from now on for you, and for all users who did customization outside what CSS can do. Of course all projected style settings shall be added as soon as possible.
Thank you!
Sorry for the delay. For me everything is ok!
Thanks again for everything!
-
This reply was modified 5 years, 6 months ago by
Jimmy Thai.
Thank you for confirmation. No worries, welcome! I’m considering reporting the bug we see in Chrome for Android. Seems it must be done directly in the browser on the phone. Did you already report it?
I can’t figure out any way to fix it other than getting it fixed by Google.
Meanwhile our 2.1.4d6 from a few minutes ago, now at https://downloads.wordpress.org/plugin/footnotes.zip is reuniting all arrow settings in the Reference container dashboard, and more importantly again, has an option for displaying a separator, Yes and COMMA by default, that you may need to set to No, as well as an option to insert a line break instead of a space between enumerated backlinks for perfect stacking. This defaults to No because horizontal enumeration is more widespread and, with many combined footnotes, the only practicable way, but you may wish to set it to Yes.
Best regards!
No this is not something I reported.
I admit I don’t know where I could do it :/
Thanks for this new pre-version, it’s really great!
Thanks for testing!
No this is not something I reported.
I admit I don’t know where I could do it :/
Assuming using Chrome: Following https://support.google.com/chrome/answer/95315?co=GENIE.Platform%3DAndroid&hl=en
- Open Chrome on Android;
- Access the page that a screenshot and logs shall be attached of;
- Tap “⁞” to the right of the address bar;
- At the bottom of the More menu, tap “Help & Feedback”;
- Tap “Send feedback”;
- Check the box to attach screenshot and logs if desired;
- Eventually tap below the screenshot thumbnail, then highlight the expand button next to the reference container label, tap OK;
- Write a bug report;
- Provide your email for convenience (and site URL unless already included in the attached logs);
- At the top right, tap the Send button.
I think this issue should get focus and a quick fix since the feature works in Chrome and Firefox for desktop, and its bug in Chrome for Android impacts usability/accessibility of footnotes content on mobile.
I’ve now accessed Google Play to install Firefox, and tapped to install also Edge, Brave and Opera. Downloads are pending. I’ll report how Footnotes functions loaded by autoload work on a smartphone in these other browsers ASAP!
-
This reply was modified 5 years, 6 months ago by pewgeuges.
-
This reply was modified 5 years, 6 months ago by pewgeuges.
-
This reply was modified 5 years, 6 months ago by pewgeuges.
I don’t know if it’s reassuring or not but looking at an old version of the footnotes plugin, I found that the bug was not present in the second article.
So it is not a browser bug in the mobile but a recent modification that caused this problem.
Small problem, I tried to download the version 2.0.8 but this one contains the modifications related to the autoloadpost.
I would have liked to download the original 2.0.8 and make the modifications to see if it works.
Do you still have this original version?
Translated with http://www.DeepL.com/Translator (free version)
Yes I have your original version with all your modifications that worked with autoload:
https://gofile.io/d/BjPtdL (expires tomorrow midnight)
It is the .zip you shared in https://wordpress.org/support/topic/auto-load-post-compatibility-update/#post-13618833
You kindly provided me with this version to do the official implementation. I must confess that given the post ID was already added to the footnote numbers in task.php (instead of the random number originally used), I re-used that code to add post ID everywhere you did, and was glad it worked, not noticing what was going on when using autoload with footnotes on a smartphone.
Else the proper version 2.0.8 with autoload support is available at https://downloads.wordpress.org/plugin/footnotes.2.0.8.zip
Whereas the last version without autoload support is 2.0.4 at https://downloads.wordpress.org/plugin/footnotes.2.0.4.zip
I’m unable to test myself because I failed to get autoload to work in a local sandbox. Surely I should try to get it in an online sandbox if that makes a difference with respect to autoload (although I can’t figure out what difference).
(As of the other browsers I still can’t see them.)
Hopefully one of the versions above will help find out what it takes to make footnotes work in autoload on a smartphone too!
