Cache 'update.min.js'

Open on Drupal.org →

Created on 20 October 2020, about 4 years ago

Updated 23 September 2023, about 1 year ago

Currently //browser-update.org/update.min.js gets injected at runtime into the document.
Why not caching update.min.js in Drupal and delivering it to clients within the normal "Drupal javascript package"?

It would safe a HTTP connection to a third-party server for visitors with a current and supported browser.

✨ Feature request

Status

Active

Version

2.1

Component

Code

Created by

🇦🇹Austria guedressel

Live updates comments and jobs are added and updated live.

Incomplete comments

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 year ago →
🇫🇷France dydave
Maybe something similar to what is being done for module AddToAny → could be a good solution for the feature requested in this ticket ?
See: ✨ Cache external addtoany JS library and update the local cache with cron Needs review

It would require quite a lot of work, since it seems to also somewhat impact existing settings fields which point to the JS scripts locations:
('source' and 'show_source', see: https://git.drupalcode.org/project/bu/-/blob/2.1.1/src/Form/SettingsForm...
whether certain scripts could be manually overridden.

It also seems be conflicting with other feature request #3213275: Support repository placed in libraries folder → (maybe the two approaches could be grouped ?).

Thanks a lot for your fedback, comments and contributions.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024