← Back to AI Insights
Gemini Executive Synthesis

Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment.

Technical Positioning
Accurate and dynamic calculation of volatile date/time functions, ensuring correct values are saved and reflect the current system clock, consistent with Excel's behavior.
SaaS Insight & Market Implications
This bug reveals a critical data integrity and calculation accuracy issue for GridCraft's browser/Wasm version. The `NOW()` and `TODAY()` functions, fundamental for dynamic date tracking, are incorrectly caching and persisting static, outdated values in saved XLSX files. This directly undermines the reliability of any spreadsheet relying on current date/time, leading to erroneous data and potentially critical business decisions based on incorrect information. For a spreadsheet application, formula accuracy and data persistence are non-negotiable. This flaw indicates a deeper problem in how volatile functions are handled during calculation and serialization, severely impacting GridCraft's credibility as an 'Excel-style' alternative.
Proprietary Technical Taxonomy
Browser NOW and TODAY fixed date current clock XLSX cached values formula entry Excel date epoch Wasm build

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 10, 2026
Repo: storytold/gridcraft
[Bug] Browser NOW and TODAY save a fixed October 7 date instead of the current clock

**Environment**

- Tested revision: 5b15827edec4adc1101576da257ec7f4d949bb5d (fetched upstream main immediately before revalidation and filing).
- macOS 26.5.2 on Apple Silicon; local release browser/Wasm build compiled through Kyoto.
- T3 Code collaborative browser: Chromium 152.0.7977.130, Electron 44.4.2, T3 Code 0.0.45.
- Fresh blank workbook; real browser clock and ordinary formula entry. No clock override or decoder/callback delay.

**Steps to reproduce**

1. Open a fresh blank browser workbook while the real date is October 10, 2026. Record `new Date().toISOString()` in the browser console.
2. Enter `=NOW()` in A1. Commit the edit and click another cell.
3. Enter `=TODAY()` in B1. Commit the edit and click another cell.
4. Save the workbook as XLSX using the normal Save shortcut.
5. Inspect `xl/worksheets/sheet1.xml` in the saved XLSX. Compare the cached values beside the literal `NOW()` and `TODAY()` formulas with the real clock, using the Excel date epoch of December 30, 1899.
6. Repeat in a second fresh blank browser page.

**Expected**

`NOW()` represents the current date and time and `TODAY()` represents the current date. A normal save must not persist a date several days earlier.

**Actual**

The saved XLSX contains `NOW()` with cached value `46302.5` and `TODAY()` with cached value `46302`. These encode October 7, 2026 at noon and October 7, respectively, while the real browser clock is October 10. Both fresh pages reproduce: actual Save actions occurred at 2026...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from storytold/gridcraft.

Extracted Positioning
Chart manipulation and resizing functionality, both via direct interaction (sizing handles) and UI controls (Format Chart Area).
Standard and expected chart editing capabilities found in modern spreadsheet applications, allowing users full control over chart presentation.
Extracted Positioning
Spreadsheet data filtering functionality, specifically auto-population of filter options and search capabilities.
Standard and expected data filtering features found in modern spreadsheet applications.
Extracted Positioning
Comprehensive keyboard accessibility and shortcut hint system, including `Alt` key navigation and a search bar.
Full keyboard-driven efficiency and discoverability of commands, matching Microsoft Excel's established accessibility standards.
Extracted Positioning
Performance and scalability for handling large XLSX files.
Robust performance and memory management for enterprise-grade spreadsheet files, comparable to Microsoft Excel.
Extracted Positioning
User interface theming, specifically the implementation of a dark mode.
Modern UI/UX standards, offering user customization for visual preferences and reducing eye strain.

Frequently Asked Questions

Market intelligence mapped to Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment..

How is Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment. positioned in the market?
Based on our AI analysis of the original developer request, its primary technical positioning is: Accurate and dynamic calculation of volatile date/time functions, ensuring correct values are saved and reflect the current system clock, consistent with Excel's behavior.
How is the developer community reacting to Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment.?
Yes, we have tracked 1 direct responses and active debates regarding this specific topic originating from GitHub Issue.
Which technical concepts are associated with Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment.?
Our proprietary extraction maps Date/time function accuracy and persistence in spreadsheet calculations, specifically for `NOW()` and `TODAY()` functions in a browser/Wasm environment. to adjacent architectural concepts including Browser NOW and TODAY, fixed date, current clock, XLSX.

Engagement Signals

1
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like Electron and Chromium by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.