[META] Re-evaluate use of Backbone.js in core

Created on 4 June 2020, over 4 years ago
Updated 2 April 2024, 8 months ago

Problem/Motivation

Backbone JS is used in core by

  • contextual links
  • toolbar

However Backbone has only had two releases since 2016, and none since Feb 2019. In addition we're using it in a fashion that is tightly bound to jQuery.

If we're aiming to move away from jQuery by Drupal 10 - should we be evaluating whether Backbone is the right solution for complex core Javascript.

Developers with knowledge of Backbone are few and far between and interest in it is very low

Proposed resolution

  • Decided we no longer want it
  • If we do decide to then:
    • Decided on migrating the functionality provided by Backbone to Vanilla JS
  • If we decide to stay put, nothing to do.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Active

Version

11.0 πŸ”₯

Component
JavascriptΒ  β†’

Last updated about 7 hours ago

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

Live updates comments and jobs are added and updated live.
  • JavaScript

    Affects the content, performance, or handling of Javascript.

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.

  • πŸ‡¬πŸ‡§United Kingdom catch

    From 11.x onwards we're down to toolbar and contextual links, it makes sense to focus on those. If the contrib modules also remove backbone eventually, we could try to port those changes across to a 10.x minor release for tour too.

Production build 0.71.5 2024