New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "[3] Pagebreak navigation cosmetic. Icons, aria-label, title, tooltips and things" #27400
Conversation
Could you please explain in more detail what breaks |
Every template loading it's own jquery could break because if you don't have a override to not load the tooltip has an additional jquery loaded. I had this problem already with another bugfix release in plg_content_pagenavigation |
Sorry but I dont see how the changes here could do that |
The only side effect introduced by that PR is the potential load of jQuery and Bootstrap on the frontend in a new location. If you’re saying that is a problem then the frontend needs to be rewritten so that it ONLY generates semantic markup with zero JavaScript enhancement or make Joomla a headless CMS and tell people they’re SOL if looking for core to be usable out-of-the-box. |
The concept is that I don't have to override each template of joomla and adding a javascript framework in the bugfix release is unexpected |
but it doesnt break anything |
it does if you don't use joomla jquery |
Afaik JQuery as well as tooltips are loaded using a JTHML function and thus should be overrideable. So if you did the JQuery and/or tooltip replacement the proper way, then this doesn't break anything at all. In the end I agree with Brian and Michael that this shouldn't be reverted. It's not really a new feature which would mandate to go into a minor release. Also, the rendered markup isn't part of our backward compatibility promise as per https://developer.joomla.org/development-strategy.html. We excluded that at the time especially in mind of issues like this one. |
Can you please provide a more detailed real word example of how this breaks a site. I have tested this on several sites that do not use joomla jquery without issue |
It's not impossible that I'm doing it wrong so what would be the prefered method not getting additional js loaded (jquery and tooltip) without overriding each layout? Or don't wanting to get jquery loaded at all? |
I am sure there are a million ways to do it but this is what I do On my main site I do
and then if I want to use bs from a cdn or something completely different I do something like
Or if I want to use bootstrap locally just a newer version then I override the files in |
I'm doing something similar in a plugin onBeforeCompileHead but got a problem on a change in the plg_content_pagenavigation |
i would say that the problem is in your code then. I tested this on three different sites all of which are not using joomla jquery in different ways and had no problems at all |
If you want to get rid of tooltips or use a different implementation, you can write a plugin which overrides the JHtml::tooltip function. I don't know exactly how it has to be done, but I'm sure I've read explanations from Michael once. |
@brianteeman @HLeithner couple of things here as I see that there are some comments that are totally wrong here:
|
I didn't tested this PR if it breaks, I only know that the last PR adding a tooltip has broken many of my sites. @dgrammatiko I don't use cdn ;-)
It's not necessary needed to do it ;-) I will test this later, but a good solution to this would be interesting (overriding jhtml correctly). And simply overriding jquery doesn't work for me because I use jquery 1.12 and 2.x (I know not necessary any longer but I still have customers requiring legacy browsers...) |
Well, you might not but Brian shared some snippet above which is totally outdated. Since Spectre and Meltdown ALL browsers run each site in isolation, meaning the cache is per site, meaning that no asset will ever be shared across different domains, even if those assets point in the same CDN (the cache bucket is per site). PS This could be educational: https://youtu.be/yOcgGSCrn-c?t=789 |
Simply remove the line |
BTW. I hate these ugly BS tooltips ;-) |
If it is about the tooltip - remove it. There are situations when they are useful or necessary but not here |
Merged #27436 as compromise. |
This PR easily breaks existing installations.