- Added functionality to generate a set of images for posting to X (formerly Twitter) with multiple images.
- Introduced a new button for creating X投稿向け画像, which generates up to 4 PNG images.
- The first image serves as a cover with a route map and summary, while subsequent images contain detailed operation information.
- Ensured images maintain a fixed size of 1080 x 1440 px and follow specific naming conventions.
- Implemented error handling for image generation failures and ensured compatibility with existing sharing features.
- Updated UI elements and styles for the new functionality, including button states and layout adjustments.
- Added necessary TypeScript type checks and validation for the new features.
- Moved the Elesite sorting logic to a new module `elesiteTrainOrder.ts`.
- Created utility functions to infer heading direction and sort Elesite entries by train number.
- Updated `injectJavascriptData` to utilize the new sorting logic and handle station sequences.
- Refactored `useElesite` to use the new sorting utility for improved readability and maintainability.
- Introduced `compile-web-script.ts` for generating JavaScript files for userscripts.
- Supports options for minification and obfuscation.
- Generates base JS, minified JS, and obfuscated userscript.
- Configurable via command line arguments and environment variables.
The 100ms pure-debounce approach caused a visible layout flash on every
render (normal mode too) because Tokyo UX was not applied for 100ms.
Fix: call setStrings() immediately in the MutationObserver callback to
prevent any flash, AND keep a 250ms delayed follow-up call to catch
async train re-renders from mock XHR setTimeout(0) responses.
Co-authored-by: Copilot <[email protected]>
Root cause: setStrings() was called synchronously in setReload(),
but the mock XHR interceptor responds via setTimeout(0), so the
site re-rendered train elements AFTER setStrings() ran, stripping
Tokyo UX styling.
Two-pronged fix:
1. setReload() now calls setStrings() again after 200ms to
re-apply Tokyo UX once the async re-render completes.
2. textInsert MutationObserver now watches with subtree:true
(childList only, not attributes - no infinite loop risk)
with 100ms debouncing, so ANY train element re-render
(including those triggered by mock XHR data) will trigger
a re-application of Tokyo UX.
- currentLines postMessage now only fires when direct
children of #disp change (line selection changes only)
Co-authored-by: Copilot <[email protected]>
Two bugs caused the Tokyo UX to be stripped/broken when mock mode was ON:
1. **Double callback firing**: the interceptor's `setTimeout` called both
`onreadystatechange.call(self)` AND `dispatchEvent(new Event('readystatechange'))`.
Since `dispatchEvent` already fires `onXxx` property handlers via the DOM event
model, the page's callback fired twice, causing a second DOM re-render that could
overwrite Tokyo UX modifications. Fixed by relying on `dispatchEvent` only (with
`ProgressEvent` for load events), with a direct-call fallback only for environments
that lack `dispatchEvent`.
2. **No double-injection guard**: if `injectedJavaScriptBeforeContentLoaded` caused
the interceptor to run more than once (e.g., `onPageStarted` fires multiple times
on Android), `_origOpen` would capture the already-patched version, leading to
unexpected behaviour. Fixed by adding `if (window.__jrsMockActive) return;` at the
top of the interceptor IIFE.
3. **Belt-and-suspenders injection**: the interceptor is now also prepended to
`injectedJavaScript` (Tokyo UX script) via the restored `mockApiConfig` parameter
on `injectJavascriptData`. The `__jrsMockActive` guard ensures it's a no-op when
`injectedJavaScriptBeforeContentLoaded` already ran it, but guarantees the
interceptor is active on platforms where IJBCL is unreliable — before
`MoveDisplayStation` triggers the first train-data poll via `onLoadEnd`.
Co-authored-by: Copilot <[email protected]>
- Scrape & analyse all 19 internal APIs of train.jr-shikoku.co.jp/sp.html
using puppeteer + Chromium remote debugging
- Save live-captured sample JSON for every API endpoint under
lib/mockApi/mockData/ (station lists, lang, timetable, train positions, etc.)
- Add lib/mockApi/webviewXhrInterceptor.ts – generates a JS snippet that
overrides XMLHttpRequest inside the WebView before page scripts run;
intercepts /g?arg1=train&arg2=train (and optionally all static APIs)
returning mock data instead of the real server response
- Add lib/mockApi/index.ts – convenience re-exports + MOCK_TRAIN_POSITIONS
constant pre-populated with captured sample data
- Extend InjectJavascriptOptions with optional mockApiConfig field
- injectJavascriptData() prepends the interceptor JS when mockApiConfig is set
- TrainMenuContext gains mockApiEnabled / setMockApiEnabled and
mockTrainPositions / setMockTrainPositions state; consumers can enable
mock mode and inject custom TrainEntry[] without reloading the app
Co-authored-by: Copilot <[email protected]>
- Introduced useElesite hook for managing elesite data and settings.
- Added elesite logo asset.
- Updated types to include elesite data structures.
- Enhanced TrainMenuProvider to manage elesite usage settings.
- Implemented data fetching and caching for elesite information.
- Added utility functions to retrieve train information from elesite data.
- Introduced `stationData.ts` to store station information including names, numbers, and features.
- Created `trainIconMap.ts` for mapping train numbers to their respective image URLs, including dynamic URLs for special trains.
- Added `trainTypeConfig.ts` to define display settings for various train types, including colors and labels for different categories.
