Original community-reported order
How does this client-side sequencer maintain track order, distinguish custom user entries, and detect deviations from the original setlist fixture?
This interactive application manages a concert setlist entirely in client-side memory using two array representations: a baseline clone of the initial 27-track concert fixture and an active mutable state array. Reordering operations swap adjacent items in the state array, custom submissions append new track objects marked with a personal boolean flag, and section toggles alternate row category metadata between 'Main set' and 'Encore'. Deviation detection performs a direct JSON serialization comparison between the active state and the baseline array, updating the header indicator to an amber status when any change is detected.
All modifications exist solely in browser session RAM; reloading the page purges personal arrangements. The underlying track listing and act divisions originate from an unverified fixture referencing a future 2026 date rather than an official concert broadcast or authoritative artist release. Song durations, set timings, and transition pacing are not modeled.
Click the 'Down' button on track 1 ('NOT OK'). The script swaps indices 0 and 1, placing 'No. 1 Obsession' first and 'NOT OK' second. The status bar immediately updates from 'Original community-reported order · 27 entries' with a green indicator to 'Personal arrangement · 27 entries' with an amber indicator dot (#dot.changed). Clicking 'Reset personal arrangement' restores the original array copy and returns the status indicator to green.
The script parses JSON from the #concert-data element to generate two distinct arrays: original and state. Each item is an object containing title, id, section ('Main set' or 'Encore'), and a personal boolean flag. Array mutations occur in place during swaps or splice operations, followed by a total re-render of the list element.
Deviation checking relies on JSON.stringify(state) !== JSON.stringify(original). When identical, the UI reports the original order with a green dot; when any property or index differs, the amber class is applied to #dot.
When generating text for clipboard copying or plain-text download, exportText() maps each element to a numbered line including its assigned section and personal tag. Taped entrance or exit tracks mentioned in metadata notes are excluded from numbered items in the active state array.
Community-reported setlist for 5 Seconds of Summer at Santander Arena on 2026-09-22. Read the original order or make a clearly labelled personal arrangement.
Live source inspected: reported 21:05–22:55. Acts: The Peak (1–3), The Fall (4–11), The Yearning (12–14), The Breakup (15–18, member solo songs), The Rise (19–20), The Beginning (21–25), The Return encore (26–27). Wrapped Around Your Finger was the secret song. Macarena and Highway to Hell are taped entrance/exit music, excluded from live-song numbering. No incomplete or out-of-order warning observed.