User tests: Successful: Unsuccessful:
Seems like this file is a leftover of earlier cleanup.
Status | New | ⇒ | Pending |
Category | ⇒ | JavaScript Administration Templates (admin) |
@HLeithner No, that PR assumes that bootstrap.js is always loaded by the template. This won't be the case for Atum...
@dgrammatiko why is there only a minified file committed then? There is no way of trying to get the original back out from this i guess
@HLeithner No, that PR assumes that bootstrap.js is always loaded by the template. This won't be the case for Atum...
You reopend #20549 do you try to fix the Situation suiteable for screenreaders?
@Hackwar @wilsonge go ahead and remove it. I already reopened #20549 and will patch the a11y concerns there.
FWIW my point was that @Bakual 's PR removing the js file was based on the assumption that Bootstrap.js will always be loaded, which of course is wrong as both Atum and Cassiopeia will be free from jQuery.js and Bootstrap.js
This PR indeed is fine since my PR back then removed all reference to load that file. I don't know why I missed the minified one. The code in that file was broken anyway.
FWIW my point was that @Bakual 's PR removing the js file was based on the assumption that Bootstrap.js will always be loaded, which of course is wrong as both Atum and Cassiopeia will be free from jQuery.js and Bootstrap.js
That's true, and explicitely mentioned in my PR back then:
Since Bootstrap is loaded anyway and it offers the same functionality, we can use just that one for now (until it gets eventually converted to a CE).
So yes, it's one roadblock to get Bootstrap removed from the template.
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-02-27 16:50:17 |
Closed_By | ⇒ | wilsonge |
Thanks!
You're breaking B/C here.
That code ensures that group buttons will work as they meant to...
In order to remove this part you need first this: #20549